[a-n]*.py: normalize doc_fragments

[russoz]

SUMMARY

Normalize doc blocks in doc_fragments.

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

plugins/doc_fragments/alicloud.py
plugins/doc_fragments/attributes.py
plugins/doc_fragments/auth_basic.py
plugins/doc_fragments/bitbucket.py
plugins/doc_fragments/consul.py
plugins/doc_fragments/dimensiondata.py
plugins/doc_fragments/dimensiondata_wait.py
plugins/doc_fragments/django.py
plugins/doc_fragments/emc.py
plugins/doc_fragments/gitlab.py
plugins/doc_fragments/hpe3par.py
plugins/doc_fragments/hwc.py
plugins/doc_fragments/ibm_storage.py
plugins/doc_fragments/influxdb.py
plugins/doc_fragments/ipa.py
plugins/doc_fragments/keycloak.py
plugins/doc_fragments/ldap.py
plugins/doc_fragments/lxca_common.py
plugins/doc_fragments/manageiq.py
plugins/doc_fragments/nomad.py

[ansibullbot]

cc @QijunPan @TommyLike @apecnascimento @chris93111 @edisonxiang @farhan7500 @freesky-edward @gautamphegde @hwDCN @niuzhenguo @xuxiaowei0512 @yanzhangi @zengchen1024 @zhongjun2
click here for bot help

[patchback]

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

❌ Failed to cleanly apply ed09295 on top of patchback/backports/stable-9/ed092956ba8bed85bbb141b6fdc90c1b19e5b503/pr-9422

Backporting merged PR #9422 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/ed092956ba8bed85bbb141b6fdc90c1b19e5b503/pr-9422 upstream/stable-9

4. Now, cherry-pick PR [a-n]*.py: normalize doc_fragments #9422 contents into that branch:

   $ git cherry-pick -x ed092956ba8bed85bbb141b6fdc90c1b19e5b503

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

   $ git cherry-pick -m1 -x ed092956ba8bed85bbb141b6fdc90c1b19e5b503

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [a-n]*.py: normalize doc_fragments #9422 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-9/ed092956ba8bed85bbb141b6fdc90c1b19e5b503/pr-9422

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]

@russoz thanks!

[patchback]

Backport to stable-10: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-10/ed092956ba8bed85bbb141b6fdc90c1b19e5b503/pr-9422

Backported as #9428

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