docs(release): update documentation links from /main to /latest (#6210)

Co-authored-by: Gergely Bräutigam <gergely.brautigam@sap.com>

.github/ISSUE_TEMPLATE/create_release.md

@@ -12,18 +12,18 @@ This Issue tracks the next ESO release. Please follow the guideline below. If an
 #### Preparation Tasks
 
 - [ ] ask in `#external-secrets-dev` if we're ready for a release cut-off or if something needs to get urgently in
-- [ ] docs: [stability & support page](https://external-secrets.io/main/introduction/stability-support/) is up to date
+- [ ] docs: [stability & support page](https://external-secrets.io/latest/introduction/stability-support/) is up to date
   - [ ] version table
   - [ ] Provider Stability and Support table
   - [ ] Provider Feature Support table
-- [ ] docs: update [roadmap page](https://external-secrets.io/main/contributing/roadmap/)
+- [ ] docs: update [roadmap page](https://external-secrets.io/latest/contributing/roadmap/)
 - [ ] tidy up [Project Board](https://github.com/orgs/external-secrets/projects/2)
   - [ ] move issues to next milestone
   - [ ] close milestone
 
 #### Release Execution
 
-- [ ] Follow the [Release Process guide](https://external-secrets.io/main/contributing/release/)
+- [ ] Follow the [Release Process guide](https://external-secrets.io/latest/contributing/release/)
 
 #### After Release Tasks
 

README.md

@@ -26,11 +26,11 @@ Multiple people and organizations are joining efforts to create a single Externa
 
 ## Documentation
 
-External Secrets Operator guides and reference documentation is available at [external-secrets.io](https://external-secrets.io). Also see our [stability and support](https://external-secrets.io/main/introduction/stability-support/) policy.
+External Secrets Operator guides and reference documentation is available at [external-secrets.io](https://external-secrets.io). Also see our [stability and support](https://external-secrets.io/latest/introduction/stability-support/) policy.
 
 ## Contributing
 
-We welcome and encourage contributions to this project! Please read the [Developer](https://www.external-secrets.io/main/contributing/devguide/) and [Contribution process](https://www.external-secrets.io/main/contributing/process/) guides. Also make sure to check the [Code of Conduct](https://www.external-secrets.io/main/contributing/coc/) and adhere to its guidelines.
+We welcome and encourage contributions to this project! Please read the [Developer](https://www.external-secrets.io/latest/contributing/devguide/) and [Contribution process](https://www.external-secrets.io/latest/contributing/process/) guides. Also make sure to check the [Code of Conduct](https://www.external-secrets.io/latest/contributing/coc/) and adhere to its guidelines.
 
 Also, please take a look our [Contribution Ladder](CONTRIBUTOR_LADDER.md) for a _very_ detailed explanation of what roles and tracks are available for people to try and help this project.
 
@@ -58,7 +58,7 @@ Please create a PR and add your company or project to our [ADOPTERS.md file](ADO
 
 ## Roadmap
 
-You can find the roadmap in our documentation: https://external-secrets.io/main/contributing/roadmap/
+You can find the roadmap in our documentation: https://external-secrets.io/latest/contributing/roadmap/
 
 ## Kicked off by
 

design/006-LTS-release.md

@@ -42,18 +42,18 @@ We'll have a release issue template that gives the release lead a task list to w
 #### Release Preparation Tasks
 
 - [ ] ask in `#external-secrets-dev` if we're ready for a release cut-off or if something needs to get urgently in
-- [ ] docs: [stability & support page](https://external-secrets.io/main/introduction/stability-support/) is up to date
+- [ ] docs: [stability & support page](https://external-secrets.io/latest/introduction/stability-support/) is up to date
   - [ ] version table
   - [ ] Provider Stability and Support table
   - [ ] Provider Feature Support table
-- [ ] docs: update [roadmap page](https://external-secrets.io/main/contributing/roadmap/)
+- [ ] docs: update [roadmap page](https://external-secrets.io/latest/contributing/roadmap/)
 - [ ] tidy up [Project Board](https://github.com/orgs/external-secrets/projects/2)
   - [ ] move issues to next milestone
   - [ ] close milestone
 
 #### Release Execution
 
-- [ ] Follow the [Release Process guide](https://external-secrets.io/main/contributing/release/)
+- [ ] Follow the [Release Process guide](https://external-secrets.io/latest/contributing/release/)
 
 #### After Release Tasks
 

docs/contributing/release.md

@@ -31,7 +31,7 @@ When doing a release it's best to start with  with the ["Create Release" issue t
 ⚠️ Note: when releasing multiple versions, make sure to first release the "old" version, then the newer version.
 Otherwise the `latest` documentation will point to the older version. Also avoid to release both versions at the same time to avoid race conditions in the CI pipeline (updating docs, GitHub Release, helm chart release).
 
-1. Make sure the [stability & support page](https://external-secrets.io/main/introduction/stability-support/) is up to date. The new version should be listed in the version table before proceeding with the release.
+1. Make sure the [stability & support page](https://external-secrets.io/latest/introduction/stability-support/) is up to date. The new version should be listed in the version table before proceeding with the release.
 1. Make sure there is no pending CI jobs running. This is to avoid promoting a stale image to a new version (we need to rely on _existing_ pushed images for release).
 1. Run `Create Release` Action to create a new release, pass in the desired version number to release.
     1. choose the right `branch` to execute the action: use `main` when creating a new release.