feat: supporting independent versions for each sub products

[elliotxx]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y

2. What is the scope of this PR (e.g. component or file name):

Tagging a new version for each sub product:

1. First, make sure the current docs version (the ./docs/[subProductNmae] directory) is ready to be frozen.
2. Enter the specified sub product name and a new version number:

npm run docusaurus docs:version:[subProductNmae] [vMAJOR.MINOR]

Example:

npm run docusaurus docs:version:docs v0.12
npm run docusaurus docs:version:ctrlmesh v0.3
npm run docusaurus docs:version:ctrlmesh v0.1

Optional sub product names:

• docs (alias for kusion)
• operating
• ctrlmesh

Format of version number: [vMAJOR.MINOR], e.g. v0.3, v0.13.

When tagging a new version of sub product, the document versioning mechanism will:

• Copy the full docs/[subProductNmae] folder contents into a new [subProductNmae]_versioned_docs/version-[versionName]/ folder.
• Create a versioned sidebars file based from your current sidebar configuration (if it exists) - saved as [subProductNmae]_versioned_sidebars/version-[versionName]-sidebars.json.
• Append the new version number to [subProductNmae]_versions.json.

More see:

• Versioning
• Docs Multi-instance

Screenshots:

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
kusionstack	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 10, 2024 8:16am

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[adohe]

/lgtm