[Needs SC review] community/other_tools_and_programs.rst: update

[Andersson007]

community/other_tools_and_programs.rst: update

Based on https://forum.ansible.com/t/should-we-revamp-the-tools-and-programs-page/39024

This PR

• Generalizes text editors info
• Leaves only VS code extensions as we're sure they're maintained
• Refers to awesome ansible for tooling
• Something doesn't even work like ansible-reviewer, so it removes tools that we're not sure about. Awesome ansible welcomes them

[gundalow]

Let's update and merge ansible-awesome before we merge this.

[gundalow]

These need adding to https://github.com/ansible-community/awesome-ansible?tab=readme-ov-file#editor-and-ide-integrations (and we should add subheadings for each editor first).

Then we can link to the awesome-ansible

[Andersson007]

ansible-community/awesome-ansible#94 <- ready for review

• Sublime: I didn't move it, doesn't feel like it has ansible support
• Ansible Inventory Grapher: Looks maintained, moved to Awesome Ansible.
• Ansible Silo: Last commit 6 years ago, opened an issue Add your project to Awesome Ansible list if relevant groupon/ansible-silo#82
• Ansigenome: Last commit 7 years ago, opened an issue Add your project to Awesome Ansible list if relevant nickjj/ansigenome#76
• ARA: Already there
• nanvault - archived
• OpsTools-ansible - archived
• ansibledb: Last commit was last year, opened an issue Add your project to Awesome Ansible list if relevant nbentoumi/ansibledb#4
• jtanner's tools: Last commit was 4 years ago, opened an issue Add your project to Awesome Ansible list if relevant jctanner/ansible-tools#5

This PR is ready for review again

[Andersson007]

The PR moving the stuff has been merged, can we merge this one?

[gundalow]

This looks great, thank you.

[Andersson007]

@samccann , added SC as codeowners, PTAL

[patchback]

Backport to stable-2.16: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply fd41e24 on top of patchback/backports/stable-2.16/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284

Backporting merged PR #2284 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.16/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284 upstream/stable-2.16

4. Now, cherry-pick PR [Needs SC review] community/other_tools_and_programs.rst: update #2284 contents into that branch:

   $ git cherry-pick -x fd41e247016bb38cb970ee2c6120a8f08ec2813b

   If it'll yell at you with something like fatal: Commit fd41e247016bb38cb970ee2c6120a8f08ec2813b is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x fd41e247016bb38cb970ee2c6120a8f08ec2813b

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [Needs SC review] community/other_tools_and_programs.rst: update #2284 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.16/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-2.17: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply fd41e24 on top of patchback/backports/stable-2.17/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284

Backporting merged PR #2284 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.17/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284 upstream/stable-2.17

4. Now, cherry-pick PR [Needs SC review] community/other_tools_and_programs.rst: update #2284 contents into that branch:

   $ git cherry-pick -x fd41e247016bb38cb970ee2c6120a8f08ec2813b

   If it'll yell at you with something like fatal: Commit fd41e247016bb38cb970ee2c6120a8f08ec2813b is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x fd41e247016bb38cb970ee2c6120a8f08ec2813b

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [Needs SC review] community/other_tools_and_programs.rst: update #2284 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.17/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-2.18: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply fd41e24 on top of patchback/backports/stable-2.18/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284

Backporting merged PR #2284 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.18/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284 upstream/stable-2.18

4. Now, cherry-pick PR [Needs SC review] community/other_tools_and_programs.rst: update #2284 contents into that branch:

   $ git cherry-pick -x fd41e247016bb38cb970ee2c6120a8f08ec2813b

   If it'll yell at you with something like fatal: Commit fd41e247016bb38cb970ee2c6120a8f08ec2813b is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x fd41e247016bb38cb970ee2c6120a8f08ec2813b

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [Needs SC review] community/other_tools_and_programs.rst: update #2284 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.18/fd41e247016bb38cb970ee2c6120a8f08ec2813b/pr-2284

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[Andersson007]

i've created manual backports, fyi