update Ansible 11 redirects

[samccann]

Update the redirects for Ansible 11 and remove the unneeded 2.10 redirects.
part of ansible/ansible-documentation#2013

[oraNod]

@samccann are you sure we can't just do a one-time renaming of 10 to latest?

I believe the point of those redirects is so any links such as this one: https://docs.ansible.com/ansible/latest/modules/k8s_module.html referenced from this blog post on ansible.com do not 404. Unfortunately that particular link still causes a 404 because the target url is out of date collections/community/kubernetes/k8s_module.html.

The current batch of redirects under the 10 folder handle links to content in the modules and plugins subdirectories for the latest branch.

The latest symlink is on the server to point to the correct version whether that is 10 or 11. By renaming the folder to latest you should be able to just rename this folder once and stop doing it every time there is a new Ansible package version.

[oraNod]

+1 to removing the 2.10 redirects.

[samccann]

Mentioned this in a chat thread but do we want to do this PR at all or just 'live with it as is' until RTD land comes in with the new batch of redirects?

[oraNod]

Mentioned this in a chat thread but do we want to do this PR at all or just 'live with it as is' until RTD land comes in with the new batch of redirects?

Not sure what you mean by RTD land. Maybe let's just go ahead and merge this and carry on with the release process as normal? Since part of the redirect consolidation includes a new collections.html page we should give community a heads up before we put that in place.

[oraNod]

This is fine. Let's go ahead and merge so we can get through the release checklist for 11. We can do new stuff on top of this.

Now that we can have confidence in the consolidated redirects there's probably no point moving the 10 subdirectory to a latest subdirectory as I mentioned in another comment. However that would prevent the need to rename the folders if we weren't going to consolidate redirects.