fix(calling): read and use mobius-ws setting from wdm

[mkesavan13]

COMPLETES CAI-7723

This pull request addresses

Reading and using the feature flag from Settings Service instead of SDK configuration to choose either HTTP requests or Mobius Requests

by making the following changes

• Reading the setting from WDM plugin with a new Util isWsFeatureEnabled
• Using the value of setting to decide whether Mobius socket should be connected in CallingClient.ts
• Using the value of setting to decide whether requests should flow through HTTP or Mobius socket
• In addition, have retained the SDK config to test this feature until the Setting is rolled out to PROD. Right now the PR is against integration in the settings service repo: https://sqbu-github.cisco.com/WebExSquared/settings-service-definitions/pull/1157

Pending Items

• Actual Testing with right config
• Removal of SDK config when the setting is PROD
• Unit Tests

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 were tested

• Tested some of the existing PROD config from the repo against webex.internal.device.settings
• An example:
  • File for the setting enable-vidcast-transcripts-generation
  • Screenshot from SDK Sample app browser console for the same setting:
    

The GAI Coding Policy And Copyright Annotation Best Practices

• GAI was not used (or, no additional notation is required)
• Code was generated entirely by GAI
• GAI was used to create a draft that was subsequently customized or modified
• Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
• Tool used for AI assistance (GitHub Copilot / Other - specify)
  • Github Copilot
  • Other - Cursor
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

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.

[mkesavan13]

May be a better naming is needed here. Suggestions are welcome

[rarajes2]

isMobiusWssFeatureEnabled or isMobiusWssFeatEnabled ?

[rarajes2]

LGTM

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 39b8c8c02b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Preserve SDK WebSocket override in APIRequest init

This constructor now relies on config.isMobiusSocketEnabled for the interim opt-in path, but production call sites still create the singleton with {webex} only (for example in CallingClient, registration/register.ts, and calling/call.ts), so the override is effectively dropped unless WDM already returns true. In the rollout scenario where WDM is still false and CallingClientConfig.isMobiusSocketEnabled is set to true, APIRequest will incorrectly route requests over HTTP, breaking the intended fallback behavior described in this change.

Useful? React with 👍 / 👎.