fix(plugin-cc): add org header to notification subscribe API for environment compatibility

[akulakum]

COMPLETES #https://jira-eng-sjc12.cisco.com/jira/browse/CAI-7499

Vidcast: https://app.vidcast.io/share/ba4ba3b8-aa90-4d5a-b67b-ba42ae17fac3

This pull request addresses

The CC SDK's webex.cc.register() was failing on certain environments (e.g., qaus1) because the WebSocket notification service was not sending the "Welcome" message after connection. Due to which, certain users were stuck on the loading screen when init widgets is called.

Root Cause: The SDK was missing the X-ORGANIZATION-ID header in the /v1/notification/subscribe request, which Agent Desktop includes.

After adding the X-ORGANIZATION-ID header to the subscribe request, the issue got resolved.

by making the following changes

1. Added X-ORGANIZATION-ID header to subscribe request (WebSocketManager.ts).
2. Updated unit tests to verify the header is included in the request

Reference: Agent Desktop implementation (aqm-notifs.ts)
The Agent Desktop sends the X-ORGANIZATION-ID header in the notification subscribe request.

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

< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

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 - Please Specify
• 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.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-4708.d3m3l2kee0btzx.amplifyapp.com