feat(plugin-meetings): Introduce SDK changes to call WCME and Locus APIs when current user steps away or returns

[antsukanova]

COMPLETES # SPARK-559645

This pull request addresses

Introduce SDK changes to call WCME and Locus APIs when the current user steps away or returns.

Related PRs:

• PR-3942: Introduce SDK changes to call WCME and Locus APIs when current user steps away or returns
• PR-3946: Step Away feature unit tests

by making the following changes

This PR only contains updates for SDK logic for the sender mostly.
Since the PR is still under development with unit tests (https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-574651), it will be presented as a draft.
Also, for now, it will contain local linking "link:../../../../webrtc-media-core" for better dx until WCME changes will be ready and release.

Also, either this PR or a separate one will be updated logic for test-app.

How to test:

1. Create PMR with guest join from SDK and native/web from your user.
2. Click on the Be right back true / Be right back false buttons in "Participants, Breakout Sessions, and Events published" section. Check the console with data about Be right back requests (for example locus-info:updateSelf->event#SELF_MEETING_BRB_CHANGED)

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 flow with good/bad requests using a sample app.
• tested flow with native / web clients and a sample app.

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[SomeBody16]

With 2 comments

[brycetham]

Overall looks good! I left a rather lengthy comment about the timing of sending the "away" state. Ideally, we'd like to send the "away" state as soon as possible, and with how it is right now, I suspect we'd see a noticeable delay.

[brycetham]

I agree with Marcin about checking transcoded meetings, though we don't have to do it in this PR (as long as you stick a TODO in there). Left a small question about the event we're emitting but other than that looks good.

[brycetham]

Looks good. Left a super minor comment and a small question, but none of them are blocking are I've approved it.