Unit tests: make set_module_args() a context manager, and remove copies of it in some tests

[felixfontein]

SUMMARY

Prepares for Data Tagging.

Adjustd version of the corresponding commit in #9833.

ISSUE TYPE

• Test Pull Request

COMPONENT NAME

various module unit tests

[felixfontein]

CC @russoz

[ansibullbot]

@felixfontein This PR was evaluated as a potentially problematic PR for the following reasons:

• More than 50 changed files.

Such PR can only be merged by human. Contact a Core team member to review this PR on IRC: #ansible-devel on Libera.chat IRC

click here for bot help

[felixfontein]

bot_skip

[patchback]

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

❌ Failed to cleanly apply a1781d0 on top of patchback/backports/stable-9/a1781d09dd59adcb009d2f9e852c2c5ecd200ef7/pr-9838

Backporting merged PR #9838 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.general.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-9/a1781d09dd59adcb009d2f9e852c2c5ecd200ef7/pr-9838 upstream/stable-9

4. Now, cherry-pick PR Unit tests: make set_module_args() a context manager, and remove copies of it in some tests #9838 contents into that branch:

   $ git cherry-pick -x a1781d09dd59adcb009d2f9e852c2c5ecd200ef7

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

   $ git cherry-pick -m1 -x a1781d09dd59adcb009d2f9e852c2c5ecd200ef7

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Unit tests: make set_module_args() a context manager, and remove copies of it in some tests #9838 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-9/a1781d09dd59adcb009d2f9e852c2c5ecd200ef7/pr-9838

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-10: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-10/a1781d09dd59adcb009d2f9e852c2c5ecd200ef7/pr-9838

Backported as #9839

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

[felixfontein]

Backport to stable-9 in #9840.