fix(docs): resolve broken anchors and links in versioned docs

[VishalPainjane]

What has changed?

This PR fixes multiple broken internal links and anchors in the versioned documentation (v2 and v3) that were causing build failures.

Specifically, it addresses:

1. Updated incorrect relative paths (swapping ../../ to ../) in quickstart guides, platform requirements, and installation docs to correctly point to server/installation.md.
2. Added explicit anchors {#capturing-testcases} to server/installation.md in both v2.0.0 and v3.0.0 docs to ensure deep linking works reliably.
3. Fixed platform specific pages (mac-linux.md, windows-wsl.md) to point to the correct installation headers.

This PR Resolves #3649 issue in keploy repo

Type of change

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Documentation update (if none of the other choices apply).

How Has This Been Tested?

I ran npm run build locally to verify that all broken link errors are resolved.

Build Output:

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.

[github-actions]

Thank you and congratulations 🎉 for opening your very first pull request in keploy

[Achanandhi-M]

Hey @VishalPainjane , the changes look good overall, but I noticed a few issues while running it. Could you please check this once? Also, please add the necessary screenshots or a short video demonstrating your changes. Thanks!

[VishalPainjane]

I have made the following updates:

• Fixed Docusaurus Config: Resolved the deprecation warning by migrating onBrokenMarkdownLinks to the markdown.hooks object in docusaurus.config.js.

Screenshot:

[Achanandhi-M]

Hey @VishalPainjane, I noticed that around 52 files were changed in this PR. I don’t think all of these changes are necessary—could you please review and limit the changes to what’s required? Thanks!

[VishalPainjane]

@Achanandhi-M, please review it now. Thanks

[Achanandhi-M]

Hey @VishalPainjane , one more change—we’ve added version 4 as well, but the updates aren’t reflected in the version 4 files yet. Could you please take a look and update those files too?

[VishalPainjane]

Hi @Achanandhi-M, I have updated the PR to include the fixes for Version 4.0.0 as requested.

Changes:

• Synced with the latest main branch to include version 4 files.
• Updated headers and anchors in versioned_docs/version-4.0.0/server/installation.md to match the fixes in other versions (Capturing Testcases → Capturing Test Cases).

I ran npm run build and npm start locally to verify that the build is successful and the dev server starts without issues.

Screenshots (Build & Start):