[Cherry Pick v2.47.1] Bump capabilities

[amit-momin]

No description provided.

[github-actions]

✅ No conflicts with other open PRs targeting release/2.47.1

[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
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[trunk-io]

     

Failed Test	Failure Summary	Logs
Test_CRE_V2_Cron_Regression	The test 'Test_CRE_V2_Cron_Regression' failed without providing specific error details.	Logs ↗︎
Test_CRE_V2_Cron_Regression/[v2]_Cron_(Beholder)_fails_when_schedule_is_below_default_limit	The test failed because the schedule value was below the default limit, causing the failure.	Logs ↗︎
Test_CRE_V2_Cron_Regression/[v2]_Cron_(Beholder)_fails_when_schedule_is_negative	The test failed because the Beholder service failed to start due to an unexpected error.	Logs ↗︎
Test_CRE_V2_Cron_Regression/[v2]_Cron_(Beholder)_fails_when_schedule_is_inappropriately_formatted	The test failed because the Beholder service could not start due to a network port conflict.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs