feat(webex-core): adding support for a custom proxy

[Tiuipuv]

This pull request addresses

Adding support for an app to set a custom proxy on all requests. The app can control this by setting the proxy configuration during init. e.g.

webex = WebexSdk.init({
  credentials: {
    supertoken: superToken
  },
  config: {
    credentials: {
      client_id,
      client_secret
    },
    proxy: 'http://proxy.company.com'
  }
});

By allowing for custom proxy it'll be easier for organizations utilizing a proxy to be able to connect to the webex sdk via NodeJS.

by making the following changes

These changes include:

• Adding a new interceptor class for webex-core, called ProxyInterceptor
• Adding the interceptor into webex-core, to run against every onRequest
• Adding new unit test file for ProxyInterceptor

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios where tested

• no proxy given (automated)
• string proxy is given in webex init config (automated)

I certified that

• I have read and followed contributing guidelines
• I discussed changes with code owners prior to submitting this pull request
• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the documentation accordingly

---

Make sure to have followed the contributing guidelines before submitting.

[Tiuipuv]

If this PR is accepted, it is recommended that the proxy documentation on this wiki page be updated to include both the websocket proxy setup as well as this new http proxy setup.

[sreenara]

@Tiuipuv, the SDK team will review this PR. Please stand-by.

[mkesavan13]

Hi @Tiuipuv

Sorry for the delay. I am looking into this PR. While I do that, could you please get the latest changes from the next branch updated to your branch?

[mkesavan13]

Also, I see Integration test failures. Please look into it. @Tiuipuv

[Tiuipuv]

PR is updated to latest next branch. I will investigate the integration failure next week. I do not have access to the 4 environment variables from my organization:

WEBEX_CLIENT_ID=""
WEBEX_CLIENT_SECRET=""
WEBEX_APPID_ORGID=""
WEBEX_APPID_SECRET=""  

is there any shared test environment I can use?

[sreenara]

PR is updated to latest next branch. I will investigate the integration failure next week. I do not have access to the 4 environment variables from my organization:

WEBEX_CLIENT_ID=""
WEBEX_CLIENT_SECRET=""
WEBEX_APPID_ORGID=""
WEBEX_APPID_SECRET=""  

is there any shared test environment I can use?

There isn't any shared test environment unfortunately. @mkesavan13 we will need to take a look at this and see if this is an existing failure.

[Tiuipuv]

Thanks for the info @sreenara. Let me know if there is anything I can do to help with this Pull Request @mkesavan13!