docs: add versioning to docs

[Sky-walkerX]

It adds the versioning feature to the docs using vitepress-versioning-plugin as well as took the snapshot of current docs into 0.1.x directory, also converts the sidebar for multi version support accordingly.
Closes #168

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1074c68

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[alexlwn123]

Nice. Since there's only one version, it just redirects to the base path without a version. Can you add another (legacy) version, even just for testing, to show what it looks like to navigate to the old docs?

Also, I don't love how the vitepress version plugins requires us to copy over every file from the doc site for every new version... I'm wondering if we could have a section of live/evergreen docs and just just track any "old"/"legacy" docs between versions. Let me know if you have any ideas.

[Sky-walkerX]

Okay, I'll try to do that.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​cross-spawn@​7.0.6
	npm/​css-loader@​7.1.4

View full report

[Sky-walkerX]

Added some legacy docs as asked.

. I'm wondering if we could have a section of live/evergreen docs and just just track any "old"/"legacy" docs between versions. Let me know if you have any ideas.

I explored and got to know that we can use git branches to manage docs. whenever we do a major change, we can make new branch and rest of the thing can be handled by hosting provider.

[MrImmortal09]

@fedimint-bot review

[fedimint-bot]

Review findings

• docs/.vitepress/sidebar.ts:50 - warning: this reverts the current live sidebar entry from Creating a wallet / createWallet back to new FedimintWallet() / constructor. Current main has moved the public docs to createWallet, so after the conflict is resolved this should preserve the new page instead of reintroducing the older constructor link.
• docs/.vitepress/sidebar.ts:158 - warning: the current FederationService sidebar entries for getEventLog() and getMetaConsensusValue() are lost here. Please carry those links and their docs forward for the latest version when rebasing, otherwise the versioned docs change will hide existing current API pages from navigation.
• docs/.vitepress/config.ts:21 - warning: current main configures transformerTwoslash with bundler/ESNext compiler options. This PR resets it to transformerTwoslash() with no options, which risks bringing back the docs type-resolution issue that config was added to fix. Please preserve the current options inside the versioned config wrapper.

Validation

• pnpm install --frozen-lockfile passed.
• pnpm --filter docs docs:build passed on this PR branch.
• GitHub reports the PR as merge-conflicting, so I could not validate the post-rebase result against current main.