Make explore experience default

[abbyhu2000]

Description

auto turn on the following config when explore is turned on

data.savedQueriesNewUI.enabled: true
opensearchDashboards.branding:
  useExpandedHeader: false
uiSettings:
  overrides:
    "theme:version": "v9"
    "home:useNewHomePage": true
    "query:enhancements:enabled": true

Issues Resolved

Screenshot

Testing the changes

Changelog

• feat: explore experience will auto turn on few other flags

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.25%. Comparing base (dfc3f48) to head (0ec7d71).
⚠️ Report is 15 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10588      +/-   ##
==========================================
- Coverage   60.25%   60.25%   -0.01%     
==========================================
  Files        4385     4385              
  Lines      116753   116753              
  Branches    19010    19010              
==========================================
- Hits        70346    70345       -1     
  Misses      41568    41568              
- Partials     4839     4840       +1     

Flag	Coverage Δ
Linux_1	26.66% <ø> (ø)
Linux_2	38.83% <ø> (ø)
Linux_3	38.42% <ø> (-0.01%)	⬇️
Linux_4	32.60% <ø> (ø)
Windows_1	26.67% <ø> (ø)
Windows_2	38.80% <ø> (ø)
Windows_3	38.42% <ø> (-0.01%)	⬇️
Windows_4	32.60% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[LDrago27]

@abbyhu2000 Are deprecations the right way to do it. it seems from prior usage as a way to just annotate settings that are unused.

OpenSearch-Dashboards/src/plugins/newsfeed/server/index.ts

Line 42 in 58f770e

deprecations: ({ unused }) => [unused('defaultLanguage')],

[abbyhu2000]

yea it was a bit of the customized usage of deprecations. But after investigation, i realized to auto-enable these settings when explore flag is on is to either use deprecations or to modify the core system code during plugin discovery phase(src/core/server/plugins/discovery/plugins_discovery.ts). I feel like changing the core plugin discovery code might be against the architecture, thus i utilize the deprecations as a hack. @ashwin-pc

[ashwin-pc]

Lets just call out this hack and mark it as not a pattern we want to follow in the comments. Given our start to build 4.0, this is just a stop gap solution with minimal changes

[ashwin-pc]

I dont think this needs to block this PR

[abbyhu2000]

Will merge this and add the comment in the following PR.

[ps48]

linked with #10490