Experimental-enabled flag improvements

[as51340]

Description

1. Validate experimental flag values
2. Log which experimental features are enabled

[master < Task] PR

• Provide the full content or a guide for the final git message
  • Improve experimental-enabled flag

CI Testing Labels

Please select the appropriate CI test labels (CI -build=build-name -test=test-suite)

Documentation checklist

• Add the documentation label tag
• Add the bug / feature label tag
• Add the milestone for which this feature is intended
  • If not known, set for a later milestone
• Write a release note, including added/changed clauses
  • Experimental-enabled flag is now validated.
  • Users can see logs which experimental features are enabled.
• Link the documentation PR here
  • [Documentation PR link]
• Tag someone from docs team in the comments

[as51340]

@kgolubic RN written above.

[gitbuda]

A bit of random thought, since it’s about logging, this PR might break packaging, specifically THIS -> double check 🙏

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[kgolubic]

I will use this for RN:

• Validation added for the experimental-enabled flag. Users can now view logs
  detailing which experimental features are enabled.
  #2106