feat(integrations):api support for gong-oauth

[hassan254-prog]

Describe your changes

Gong recently made changes to their API. Gong-oauth now uses api_base_url_for_customer, which varies for each customer, as its base_url for proxy requests. This parameter is returned in the response of generate-customer-token when exchanging code for an access token.

Issue ticket number and link

Checklist before requesting a review (skip if just adding/editing APIs & templates)

• I added tests, otherwise the reason is:
• I added observability, otherwise the reason is:
• I added analytics, otherwise the reason is:

[khaliqgant]

@hassan254-prog should this still be in draft?

[hassan254-prog]

Robin had suggested I place it in draft just in case there is more work to it.

[tconlin]

@hassan254-prog Will this automatically work for all customers? Will there ever be a situation where a sync will fail because a customer does not yet have api_base_url_for_customer defined?

[hassan254-prog]

@tconlin , according to this thread, whenever the code is exchanged for an access token during authorization, as part of data residency support, the api_base_url_for_customer will be generated and returned in response. Have you gotten the chance to test this?

[tconlin]

@rguldener Can we bring this out of drafts?

[rguldener]

@rguldener Can we bring this out of drafts?

Sure! I only suggested draft initially because there might have been more work needed. Feel free to move this forward.

[bastienbeurier]

I'm concerned this will break existing connections that don't have the api_base_url_for_customer field populated in the connection config.

Is there a way to fall back to https://api.gong.io?

Would something like ${connectionConfig.api_base_url_for_customer || 'https://api.gong.io} work?

[hassan254-prog]

@bastienbeurier , I will do some test on this and see if the platform will handle such case. Incase of any changes to the platform, I will add them to this pull request. Thank you.