Problem Description: Community users have linked to their collections and roles inside their blogs, documentation, etc.

Links to collections and roles used in legacy galaxy will not resolve to the new beta galaxy which use different urls for the UI. While this is beyond "keep automation working" it would be good to mitigate broken links from the community.

Proposed Solution:

Some very draft options to think about:

1. Do this is django with a very lightweight route that looks for a matching collection if it exists, then a role, then redirects accordingly.
   1. There are cons to having this be a fully maintained thing to suggest people use "https://galaxy.ansible.com/{namespace}/{name}" because it ignores repos and there may be a future requirement put content in different repos, and this "shortcut" has a potential to be confusing and/or wrong.
2. Single redirect https://galaxy.ansible.com/\{namespace}/{name} to /ui/repo/published/{namespace}/{name}/. Then for 404s on /ui/repo/published/{namespace}/{name}/ display a special 404 message or try to redirect to /ui/legacy/roles/{namespace}/{name}/
3. Many redirects in beta-galaxy that will take most popular content from legacy and route to the new path.Maybe add redirects for 500-1,000 roles but not 34,000 roles - This would only be viable if it does not need to be maintained