##### SUMMARY
As a part of the [Consolidating Ansible discussion platforms
initiative](https://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812),
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 your forum group and/or tags related to the collection,
please update corresponding lines by suggesting changes to the PR.
- If the collection is not present on the Ansible forum yet, please
check out the existing [tags](https://forum.ansible.com/tags) and
[groups](https://forum.ansible.com/g) - use what suits your collection.
If there is no appropriate tag, please [request
one](https://forum.ansible.com/t/requesting-a-forum-group/503/17). You
can also request a group there as a WG if needed. Then update
corresponding lines by suggesting changes to the PR.
- Presence in the forum will soon likely become a part of the Collection
inclusion requirements.
##### ISSUE TYPE
- Docs Pull Request
##### COMPONENT NAME
README.md
---------
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: jo <ljonas@riseup.net>
##### SUMMARY
The current release process for this project requires multiple manual
local steps to prepare and then tag the release. This introduces the
standard release-please workflow we have in most of our integrations.
Release-please will open a new PR whenever there is a releasable change
and it updates the CHANGELOG & other files automatically in this PR.
Once the PR is merged a new tag is created.
This repository has some additional complexity as it uses
`antsibull-changelog` to maintain the user-facing changelog. This is
implemented ina second job in the `release-please` workflow which
executes when the release-please PR is updated and then runs
`antsibull-changelog release` against the version. The resulting changes
are pushed as a second commit to the same PR.
##### SUMMARY
Add Github version badge and Ansible Galaxy version. Fix the azure build
status to target the main branch.
We can check that the Github and Ansible Galaxy version match by looking
at the badges.
