Remove Ansible 2.9 & 2.10

[jchancojr]

SUMMARY

Remove Ansible 2.9 & 2.10

[hunleyd]

lgtm, thanks @jchancojr !

[Andersson007]

@jchancojr thanks! Couple of suggestions from me.

[jchancojr]

Thanks, @Andersson007! Will review and do the needful.

[patchback]

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

❌ Failed to cleanly apply 6f0d58d on top of patchback/backports/stable-1/6f0d58d6715ed3ed204ab50bd0f23d726b537de9/pr-245

Backporting merged PR #245 into main

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-collections/community.postgresql.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-1/6f0d58d6715ed3ed204ab50bd0f23d726b537de9/pr-245 upstream/stable-1

4. Now, cherry-pick PR Remove Ansible 2.9 & 2.10 #245 contents into that branch:

   $ git cherry-pick -x 6f0d58d6715ed3ed204ab50bd0f23d726b537de9

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

   $ git cherry-pick -m1 -x 6f0d58d6715ed3ed204ab50bd0f23d726b537de9

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove Ansible 2.9 & 2.10 #245 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-1/6f0d58d6715ed3ed204ab50bd0f23d726b537de9/pr-245

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]

@jchancojr seems that there are conflicts, would you like to try to backport your PR to stable-1 manually?
alternatively you could use https://docs.ansible.com/ansible/devel/community/development_process.html#backporting-merged-prs-in-ansible-base (use main instead of devel).
if you have no time, please let me know

[jchancojr]

Hi, @Andersson007

I'll get the backport to stable-1 done manually. No problem