Fix backporting gaps to prevent old docs versions from showing up in search

[lasomethingsomething]

What changed?

This PR aims to close the backporting gap between v0.24.0 and v0.25.0 that is causing people to end up in the v0.24.0 version of the docs via searches.

Why was this change made?

So users don't get taken to old user docs pages.

How was this change implemented?

This updates v0.24.0 to include URLs, file names, sidebar references, and link updates made in v0.25.0.

How did you validate the change?

Ran yarn start a bunch of times until I got a clean result.

Documentation Changes

It's all about doc changes.

[enekofb]

Lauri,

what is the user flow where they end up in v0.24:

• user goes to docs and click search, finds something -> click -> goes to v0.24 version -> docs not found or
• something else?

Btw, it seems there is some build issue see here https://github.com/weaveworks/weave-gitops/actions/runs/6112250021/job/16589310309

[lasomethingsomething]

@enekofb The user flow is that a person will either come to the old pages through Google search or end up on these old pages after clicking inside our docs and unexpectedly being taken there. I'm aware of the build issues, I attributed it to this being a change affecting docs from several releases ago and was waiting till today to ask for insight/help in resolving.

[enekofb]

I'm aware of the build issues, I attributed it to this being a change affecting docs from several releases ago and was waiting till today to ask for insight/help in resolving.

not sure if useful, but have raised an example of link fix here

in case you want to review how to view and fix them locally (in case you are not familiar) feel free to ping me

[enekofb]

Some suggestions were added on the links. I definitely support not doing backporting changes going forward unless there in special occasions.