docs: migrate RTD URLs to docs.ansible.com (#16189)

* docs: update readthedocs.io URLs to docs.ansible.com equivalents

🤖 Generated with Claude Code
https://claude.ai/code

Co-Authored-By: Claude <noreply@anthropic.com>

* Update Bullhorn newsletter link in communication docs

---------

Co-authored-by: Claude <noreply@anthropic.com>

docs/capacity.md

@@ -68,7 +68,7 @@ The value `fork_per_cpu` can be controlled by setting the AWX settings value (or
 
 When selecting the capacity, it's important to understand how each job type affects it.
 
-It's helpful to understand what `forks` mean to Ansible: http://docs.ansible.com/ansible/latest/intro_configuration.html#forks
+It's helpful to understand what `forks` mean to Ansible: https://docs.ansible.com/projects/ansible/latest/intro_configuration.html#forks
 
 The default forks value for ansible is `5`. However, if AWX knows that you're running against fewer systems than that, then the actual concurrency value
 will be lower.

docs/collections.md

@@ -82,7 +82,7 @@ job runs. It will populate the cache id set by the last "check" type update.
 
 For details on how Galaxy servers are configured in Ansible in general see:
 
-https://docs.ansible.com/ansible/devel/user_guide/collections_using.html
+https://docs.ansible.com/projects/ansible/devel/user_guide/collections_using.html
 (if "devel" link goes stale in the future, it is for Ansible 2.9)
 
 You can specify a list of zero or more servers to download roles and

docs/credentials/multi_credential_assignment.md

@@ -162,7 +162,7 @@ is the ability to assign multiple Vault credentials to a Job Template run.
 
 This specific use case covers Ansible's support for multiple Vault passwords for
 a playbook run (since Ansible 2.4):
-http://docs.ansible.com/ansible/latest/vault.html#vault-ids-and-multiple-vault-passwords
+https://docs.ansible.com/projects/ansible/latest/vault.html#vault-ids-and-multiple-vault-passwords
 
 Vault credentials in AWX now have an optional field, `vault_id`, which is
 analogous to the `--vault-id` argument to `ansible-playbook`.  To run

docs/docsite/rst/404.rst

@@ -12,8 +12,8 @@ The page you are looking for is not in the current AWX documentation.
 You can find different versions of the AWX documentation by opening the Read the Docs fly out menu at the bottom right.
 For your convenience, here are some links:
 
-* `AWX latest <https://ansible.readthedocs.io/projects/awx/en/latest/>`_ documentation, includes release notes and known issues, contributor's guide, and API reference.
-* `AWX 24.6.1 <https://ansible.readthedocs.io/projects/awx/en/24.6.1/>`_ documentation, includes release notes, contributor's guide, AWX quickstart, user guide, API reference, and administrator guide.
+* `AWX latest <https://docs.ansible.com/projects/awx/en/latest/>`_ documentation, includes release notes and known issues, contributor's guide, and API reference.
+* `AWX 24.6.1 <https://docs.ansible.com/projects/awx/en/24.6.1/>`_ documentation, includes release notes, contributor's guide, AWX quickstart, user guide, API reference, and administrator guide.
 
 If you have more questions or still can't find the docs you're looking for, join the `Ansible Forum <https://forum.ansible.com>`_.
 Here are some useful links for AWX users:

docs/docsite/rst/contributor/communication.rst

@@ -22,7 +22,7 @@ Join the `Ansible Forum <https://forum.ansible.com>`_ as a single starting point
 
 * `Get Help <https://forum.ansible.com/c/help/6>`_: get help or help others. Please add appropriate tags if you start new discussions, for example `awx`, `ee`, and  `documentation`.
 * `Posts tagged with 'awx' <https://forum.ansible.com/tag/awx>`_: subscribe to participate in project/technology-related conversations. There are other related tags in the forum you can use.
-* `Bullhorn newsletter <https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn>`_: used to announce releases and important changes.
+* `Bullhorn newsletter <https://docs.ansible.com/projects/ansible/latest/community/communication.html#the-bullhorn>`_: used to announce releases and important changes.
 * `Social Spaces <https://forum.ansible.com/c/chat/4>`_: gather and interact with fellow enthusiasts.
 * `News & Announcements <https://forum.ansible.com/c/news/5>`_: track project-wide announcements including social events.
 

docs/docsite/rst/contributor/work_items.rst

@@ -18,7 +18,7 @@ Fixing and updating the documentation are always appreciated, so reviewing the b
 Things to know prior to submitting revisions
 ----------------------------------------------
 
-- Please follow the `Ansible code of conduct <http://docs.ansible.com/ansible/latest/community/code_of_conduct.html>`_ in all your interactions with the community.
+- Please follow the `Ansible code of conduct <https://docs.ansible.com/projects/ansible/latest/community/code_of_conduct.html>`_ in all your interactions with the community.
 - All doc revisions or additions are done through pull requests against the ``devel`` branch.
 - You must use ``git commit --signoff`` for any commit to be merged, and agree that usage of ``--signoff`` constitutes agreement with the terms of `DCO 1.1 <https://github.com/ansible/awx/blob/devel/DCO_1_1.md>`_.
 - Take care to make sure no merge commits are in the submission, and use ``git rebase`` vs ``git merge`` for this reason.

docs/execution_environments.md

@@ -4,8 +4,8 @@ All jobs use container isolation for environment consistency and security.
 Compliant images are referred to as Execution Environments (EE)s.
 
 For more information about the EE technology as well as how to build and test EEs, see:
-- [Getting started with Execution Environments guide](https://ansible.readthedocs.io/en/latest/getting_started_ee/index.html)
-- [Ansible Builder documentation](https://ansible.readthedocs.io/projects/builder/en/latest/)
+- [Getting started with Execution Environments guide](https://docs.ansible.com/en/latest/getting_started_ee/index.html)
+- [Ansible Builder documentation](https://docs.ansible.com/projects/builder/en/latest/)
 
 The Execution Environment model has an `image` field for the image identifier which will be used by jobs.
 The job details view will link to the execution environment that the job uses.