Synchronise tox configuration between amazon.aws and community.aws

[tremble]

SUMMARY

tox configs needed a little cleanup to ensure that things were consistently in the import path when running pylint.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

pyproject.toml
tests/unit/conftest.py
tox.ini

ADDITIONAL INFORMATION

See also: ansible-collections/community.aws#2219

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/6197571bbf144b2c8e6f5a22af54ae40

✔️ ansible-galaxy-importer SUCCESS in 3m 27s
✔️ build-ansible-collection SUCCESS in 10m 33s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/f00938b5c38a4138929cc173937d31c8

✔️ ansible-galaxy-importer SUCCESS in 3m 27s
✔️ build-ansible-collection SUCCESS in 10m 19s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/2ec8576dc99d4a9994012810f24a9503

✔️ ansible-galaxy-importer SUCCESS in 3m 30s
✔️ build-ansible-collection SUCCESS in 10m 16s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/05df55d6894e486bb240cb210763b082

✔️ ansible-galaxy-importer SUCCESS in 3m 43s
✔️ build-ansible-collection SUCCESS in 10m 43s

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).
https://ansible.softwarefactory-project.io/zuul/buildset/aebdf4bb902444df923224f7e98470b2

✔️ ansible-galaxy-importer SUCCESS in 3m 36s
✔️ build-ansible-collection SUCCESS in 10m 09s

[patchback]

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

❌ Failed to cleanly apply 62ea880 on top of patchback/backports/stable-9/62ea880c6c5bb78dfbe2134b03fa7138acb516ec/pr-2486

Backporting merged PR #2486 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/amazon.aws.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/62ea880c6c5bb78dfbe2134b03fa7138acb516ec/pr-2486 upstream/stable-9

4. Now, cherry-pick PR Synchronise tox configuration between amazon.aws and community.aws #2486 contents into that branch:

   $ git cherry-pick -x 62ea880c6c5bb78dfbe2134b03fa7138acb516ec

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

   $ git cherry-pick -m1 -x 62ea880c6c5bb78dfbe2134b03fa7138acb516ec

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Synchronise tox configuration between amazon.aws and community.aws #2486 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-9/62ea880c6c5bb78dfbe2134b03fa7138acb516ec/pr-2486

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.