FMEPRD-306 Add Warehouse Native Experimentation Beta Documentation

[alai97]

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.

Description

• Please describe your changes: Adds beta documentation (a new doc set) for Warehouse Native Experimentation and a release note. Also adds tooltips (thanks Richard!) and diagrams (no screenshots yet).
• Jira/GitHub Issue numbers (if any): https://harness.atlassian.net/browse/FMEPRD-306
• Preview links/images (Internal contributors only): https://68e804ec9c504d025149fd8a--harness-developer.netlify.app/docs/feature-management-experimentation/warehouse-native

PR lifecycle

We aim to merge PRs within one week or less, but delays happen sometimes.

If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.

PRs must meet these requirements to be merged:

• Successful preview build.
• Code owner review.
• No merge conflicts.
• Release notes/new features docs: Feature/version released to at least one prod environment.

[bot-gitexp-user]

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68e804ec9c504d025149fd8a--harness-developer.netlify.app

[bot-gitexp-user]

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68e95a4e78d7ceff0f777ea3--harness-developer.netlify.app

[richardblack-Harness]

A few nits around style guide adherence and strongly tab usage for less toil for users and sharability.

[richardblack-Harness]

Consider synced tabs throughout so users only have to select the tab item once for the whole doc. https://docusaurus.io/docs/markdown-features/tabs#syncing-tab-choices

Adding queryString to tabs is also a great addition for sharability (also in the above linked doc)

The example I spotted was for Column Mapping and Hardcoded Values tabs

[richardblack-Harness]

Consider a dedicated document with all of these steps either on one page or in sequence. The link should direct to the first one, which in turn will direct to the next one, etc.

Having instructions that have the user go back and forward to check which step is next can become frustrating.

[richardblack-Harness]

Style guide adherence: Use "Go to x to do y" approach when linking: https://harness.atlassian.net/wiki/spaces/DOCS/pages/21544468526/Harness+documentation+style+guide#Links

While it can come across as authoritative, we're lining the user up for success and should take the approach of instructing rather than suggesting, as they are more likely to gain understanding or a more in-depth use case if they follow our instructions.