fix: bump internal-media-core to 2.29.0

[SomeBody16]

COMPLETES SPARK-833463

This pull request addresses

Keeping SDK media dependencies aligned with the latest @webex/internal-media-core release so meetings, calling, and media helpers pick up upstream media diagnostics and stats improvements.

by making the following changes

Dependency updates

Package	Previous	New	Updated in
@webex/internal-media-core	2.28.2	2.29.0	media-helpers, plugin-meetings, calling
@webex/web-client-media-engine (transitive)	3.42.1	3.43.0	via yarn.lock

No SDK source code changes — this PR only bumps dependency versions and refreshes the lockfile.

What's new upstream (2.28.2 → 2.29.0)

1. Remote audio first-frame delay detection (internal-media-core)

StatsMonitor now detects when inbound remote audio takes too long to produce its first decoded frame after media monitoring starts.

• Adds REMOTE_AUDIO_FIRST_FRAME_DELAY_THRESHOLD_MS (5000 ms)
• Adds new inbound audio issue subtype: InboundAudioIssueSubTypes.REMOTE_AUDIO_FIRST_FRAME_DELAY
• Adds StatsMonitor.start() / StatsMonitor.stop() lifecycle hooks to anchor the measurement window
• After 5 s, if no firstAudioFrameTimestamp is seen (or delay exceeds threshold), emits an inbound audio issue event

SDK impact: meetings and calling that use StatsAnalyzer / StatsMonitor can now surface this via the existing MEDIA_INBOUND_AUDIO_ISSUE_DETECTED event (media:inboundAudio:issueDetected). media-helpers re-exports the new InboundAudioIssueSubTypes value.

2. Inbound RTP stats enrichment (web-client-media-engine 3.43.0)

WCME now maps receivedAudioFrameCount from encoded stream metadata into inbound RTP stats. This lets StatsMonitor tell whether the encoded audio transform path is active before evaluating first-frame delay.

SDK impact: improved media quality diagnostics without API changes in the SDK itself.

Affected SDK packages

• @webex/media-helpers — inherits updated WCME/media-core types and re-exports
• @webex/plugin-meetings — meeting media connections and stats analyzer behavior
• @webex/calling — calling media stack

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

• yarn install completes successfully with updated lockfile
• yarn workspace @webex/media-helpers test:unit
• yarn workspace @webex/plugin-meetings test:unit
• yarn workspace @webex/calling test:unit
• Join a meeting and verify remote audio plays normally

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.