✨ add support for remote_configuration_id in view events

[gogusarov]

Motivation

Currently we have no per-session signal in the collected data showing whether a customer actually has Remote Configuration enabled. Surfacing the remote configuration id on view events lets us determine RC adoption directly from events.

Changes

Resolve remoteConfigurationId onto RumConfiguration (via the existing helper) and emit it as remote_configuration_id inside _dd.configuration on view events.

Test instructions

1. add remote-config.json file to sandbox directory
2. update parameters, passed to DD_RUM.init adding remoteConfiguration: { id: 'remote-config-test' }, remoteConfigurationProxy: '/remote-config.json'
3. check that _dd.configuration.remote_configuration_id is sent in a view event and has a value of remote-config-test

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change.
• Added e2e/integration tests for this change.
• Updated documentation and/or relevant AGENTS.md file

[datadog-prod-us1-4]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 77.20% (+0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 5b0a597 | Docs | Datadog PR Page | Give us feedback!}

[cit-pr-commenter-54b7da]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	172.61 KiB	172.69 KiB	+76 B	+0.04%	✅
Rum Profiler	8.22 KiB	8.22 KiB	0 B	0.00%	✅
Rum Recorder	21.14 KiB	21.14 KiB	0 B	0.00%	✅
Logs	54.58 KiB	54.58 KiB	0 B	0.00%	✅
Rum Slim	130.44 KiB	130.52 KiB	+76 B	+0.06%	✅
Worker	22.96 KiB	22.96 KiB	0 B	0.00%	✅