[oc ... onep]*.py: normalize docs

[russoz]

SUMMARY

Normalize doc blocks.

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

plugins/modules/ocapi_command.py
plugins/modules/ocapi_info.py
plugins/modules/oci_vcn.py
plugins/modules/odbc.py
plugins/modules/office_365_connector_card.py
plugins/modules/ohai.py
plugins/modules/omapi_host.py
plugins/modules/one_host.py
plugins/modules/one_image.py
plugins/modules/one_image_info.py
plugins/modules/one_service.py
plugins/modules/one_template.py
plugins/modules/one_vm.py
plugins/modules/one_vnet.py
plugins/modules/oneandone_firewall_policy.py
plugins/modules/oneandone_load_balancer.py
plugins/modules/oneandone_monitoring_policy.py
plugins/modules/oneandone_private_network.py
plugins/modules/oneandone_public_ip.py
plugins/modules/oneandone_server.py
plugins/modules/onepassword_info.py

[ansibullbot]

cc @None @Rylon @aajdinov @abakanovskii @amasolov @edevenport @ilicmilan @john-westcott-iv @manojmeda @marc-sensenich @meerkampdvv @mikemoerk @mross22 @nalsaber @nerzhul @nilsding @rohitChaware @rsmontero @rvalle @xorel
click here for bot help

[patchback]

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

❌ Failed to cleanly apply 8833057 on top of patchback/backports/stable-9/88330575ff648276f37112f8a5eff7c0fc686add/pr-9382

Backporting merged PR #9382 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/88330575ff648276f37112f8a5eff7c0fc686add/pr-9382 upstream/stable-9

4. Now, cherry-pick PR [oc ... onep]*.py: normalize docs #9382 contents into that branch:

   $ git cherry-pick -x 88330575ff648276f37112f8a5eff7c0fc686add

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

   $ git cherry-pick -m1 -x 88330575ff648276f37112f8a5eff7c0fc686add

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

   $ git push origin patchback/backports/stable-9/88330575ff648276f37112f8a5eff7c0fc686add/pr-9382

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/88330575ff648276f37112f8a5eff7c0fc686add/pr-9382

Backported as #9408

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