[DX-2884] Remote CHiP Ingress test sink

[Tofel]

Adds standalone CHiP test sink support across local CLI and remote agent flows, so sink lifecycle and event visibility can be managed consistently in mixed/local/remote CRE setups.

Summary

• Adds env beholder sink command wiring and standalone sink lifecycle handling in CLI (start/stop/status/events).
• Introduces remote agent CHiP sink lifecycle APIs and runtime/status integration.
• Adds remote client wrappers for CHiP sink operations.
• Adds shared CHiP event decoding logic (event_decode) and reusable sink server package for runtime usage.
• Persists remote agent runtime state needed for follow-up sink operations.
• Updates test helpers and adds unit/handler tests for sink lifecycle + remote client behavior.

[github-actions]

✅ No conflicts with other open PRs targeting dx-2884-dx-2901-dx-2911-hybrid-local-cre-env

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[trunk-io]

     

Failed Test	Failure Summary	Logs
Test_CRE_GRPCSource_AuthRejection	The test failed due to an unspecified error during execution, with no clear indication of the specific failure cause.	Logs ↗︎
Test_CRE_V2_Suite_Bucket_C	The test 'Test_CRE_V2_Suite_Bucket_C' failed during execution.	Logs ↗︎
Test_CRE_V2_Suite_Bucket_C/[v2]_Cron_Beholder_-_workflow-gateway-capabilities	The test failed because the Beholder state file was not found, causing the system to fail to start properly.	Logs ↗︎
Test_CRE_V2_Cron_Regression/[v2]_Cron_(Beholder)_fails_when_schedule_is_negative	The test failed because the Beholder state file was not found, causing the process to timeout.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs