📖 Fix docs redirect for ClusterResourceSet

[Surya-7890]

What this PR does / why we need it:

The url for ClusterResourceSet points to an invalid page, as the feature is moved from experimental stage and made generally available. A redirect rule is written in the netlify.toml file to redirect the requests to the correct url.

Which issue(s) this PR fixes :
Fixes #12132

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Surya-7890 / name: Surya (63f779f)

[k8s-ci-robot]

Welcome @Surya-7890!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Surya-7890. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mboersma]

/ok-to-test
/area documentation
/release-note-none

[mboersma]

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

@Surya-7890 could you remove this line from the commit message?

Fixes: https://github.com/kubernetes-sigs/cluster-api/issues/12132

[sbueringer]

Thx!

Change is fine otherwise

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Surya-7890]

@mboersma @sbueringer Removed Fixes: #12132 from the commit message!

[sbueringer]

Thx!

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 1ec32a66cb88e303867d96d526d0ca2a6f201d34

[sbueringer]

/cherry-pick release-1.10

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #12457

In response to this:

/cherry-pick release-1.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[sbueringer]

Verified, works. Thx!