Add stricter upperbound for galaxy-importer to account for dropping of py3.8

[gerrod3]

Our older images <core3.49 use python3.8. A recent release of galaxy-importer now uses code not present in py3.8, and it seems they haven't been testing 3.8 for a while. So restrict to last known supported version: ansible/galaxy-importer@109c1ee

[patchback]

Backport to 0.16: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 2e4d129 on top of patchback/backports/0.16/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084

Backporting merged PR #2084 into 0.20

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/pulp/pulp_ansible.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/0.16/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084 upstream/0.16

4. Now, cherry-pick PR Add stricter upperbound for galaxy-importer to account for dropping of py3.8 #2084 contents into that branch:

   $ git cherry-pick -x 2e4d1296644193213b8bf36f5cce54f6cb3e2c31

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

   $ git cherry-pick -m1 -x 2e4d1296644193213b8bf36f5cce54f6cb3e2c31

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Add stricter upperbound for galaxy-importer to account for dropping of py3.8 #2084 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/0.16/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084

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.

[mdellweg]

#2085

[patchback]

Backport to 0.18: 💚 backport PR created

✅ Backport PR branch: patchback/backports/0.18/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084

Backported as #2096

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

[patchback]

Backport to 0.15: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 2e4d129 on top of patchback/backports/0.15/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084

Backporting merged PR #2084 into 0.20

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/pulp/pulp_ansible.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/0.15/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084 upstream/0.15

4. Now, cherry-pick PR Add stricter upperbound for galaxy-importer to account for dropping of py3.8 #2084 contents into that branch:

   $ git cherry-pick -x 2e4d1296644193213b8bf36f5cce54f6cb3e2c31

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

   $ git cherry-pick -m1 -x 2e4d1296644193213b8bf36f5cce54f6cb3e2c31

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Add stricter upperbound for galaxy-importer to account for dropping of py3.8 #2084 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/0.15/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084

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.