yamllint cleanup/config

[tremble]

SUMMARY

Some minor yamllint cleanup, and configuration. (Doesn't touch integration tests yet...)

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

.yamllint
meta/runtime.yml
changelogs/config.yaml

ADDITIONAL INFORMATION

[softwarefactory-project-zuul]

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

✔️ ansible-galaxy-importer SUCCESS in 8m 31s
✔️ build-ansible-collection SUCCESS in 13m 08s

[softwarefactory-project-zuul]

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

✔️ ansible-galaxy-importer SUCCESS in 4m 41s
✔️ build-ansible-collection SUCCESS in 14m 03s

[patchback]

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

❌ Failed to cleanly apply 520019d on top of patchback/backports/stable-6/520019de0e1e8702867bd085a6b3352383a8c0a6/pr-1745

Backporting merged PR #1745 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-6/520019de0e1e8702867bd085a6b3352383a8c0a6/pr-1745 upstream/stable-6

4. Now, cherry-pick PR yamllint cleanup/config #1745 contents into that branch:

   $ git cherry-pick -x 520019de0e1e8702867bd085a6b3352383a8c0a6

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

   $ git cherry-pick -m1 -x 520019de0e1e8702867bd085a6b3352383a8c0a6

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR yamllint cleanup/config #1745 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-6/520019de0e1e8702867bd085a6b3352383a8c0a6/pr-1745

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.