[stable-2] Make current_container_facts work with newer Docker versions and latest ansible-test container changes

[felixfontein]

SUMMARY

Backport of the bugfix part of #510 to stable-2.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

current_container_facts

[github-actions]

Docs Build 📝

Thank you for contribution!✨

This PR has been merged and your docs changes will be incorporated when they are next published.

[kristianheljas]

Backport is functionally identical, good to go

[patchback]

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

❌ Failed to cleanly apply 3da9aa3 on top of patchback/backports/stable-1/3da9aa3b9c0b1fe166af16e090419fe5ca9feca5/pr-512

Backporting merged PR #512 into stable-2

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.docker.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/3da9aa3b9c0b1fe166af16e090419fe5ca9feca5/pr-512 upstream/stable-1

4. Now, cherry-pick PR [stable-2] Make current_container_facts work with newer Docker versions and latest ansible-test container changes #512 contents into that branch:

   $ git cherry-pick -x 3da9aa3b9c0b1fe166af16e090419fe5ca9feca5

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

   $ git cherry-pick -m1 -x 3da9aa3b9c0b1fe166af16e090419fe5ca9feca5

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [stable-2] Make current_container_facts work with newer Docker versions and latest ansible-test container changes #512 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-1/3da9aa3b9c0b1fe166af16e090419fe5ca9feca5/pr-512

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.

[felixfontein]

@kristianheljas thanks for checking this one!