README: Add Communication section with Forum information

[Andersson007]

Dear maintainers,
As a part of the Consolidating Ansible discussion platforms initiative, this PR adds the communication section template defined by the community to the README. Similar PRs are being raised across all included collections under the ansible-collection org for now.

-If you have other forum group and/or tags related to the collection that i didn't spot, please update the PR.

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

README.md

[softwarefactory-project-zuul]

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

✔️ ansible-galaxy-importer SUCCESS in 4m 06s
✔️ build-ansible-collection SUCCESS in 5m 40s

[patchback]

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

❌ Failed to cleanly apply 445d367 on top of patchback/backports/stable-5/445d3670598e774ca3ed2a5b0402485c666adbfe/pr-774

Backporting merged PR #774 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/kubernetes.core.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-5/445d3670598e774ca3ed2a5b0402485c666adbfe/pr-774 upstream/stable-5

4. Now, cherry-pick PR README: Add Communication section with Forum information #774 contents into that branch:

   $ git cherry-pick -x 445d3670598e774ca3ed2a5b0402485c666adbfe

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

   $ git cherry-pick -m1 -x 445d3670598e774ca3ed2a5b0402485c666adbfe

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR README: Add Communication section with Forum information #774 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-5/445d3670598e774ca3ed2a5b0402485c666adbfe/pr-774

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.