Update Readme to match the template

[GomathiselviS]

SUMMARY

Refer: https://issues.redhat.com/browse/ACA-1749
This PR updates the README doc to match the template

ISSUE TYPE

• Bugfix Pull Request
• Docs Pull Request
• Feature Pull Request
• New Module Pull Request

COMPONENT NAME

ADDITIONAL INFORMATION

[softwarefactory-project-zuul]

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

✔️ ansible-galaxy-importer SUCCESS in 4m 53s
✔️ build-ansible-collection SUCCESS in 6m 03s

[softwarefactory-project-zuul]

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

✔️ ansible-galaxy-importer SUCCESS in 4m 39s
✔️ build-ansible-collection SUCCESS in 5m 50s

[softwarefactory-project-zuul]

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

✔️ ansible-galaxy-importer SUCCESS in 4m 22s
✔️ build-ansible-collection SUCCESS in 5m 54s

[patchback]

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

❌ Failed to cleanly apply fdb8af7 on top of patchback/backports/stable-3/fdb8af7ca9dc96a426cc0ff977119676dad1aff8/pr-767

Backporting merged PR #767 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-3/fdb8af7ca9dc96a426cc0ff977119676dad1aff8/pr-767 upstream/stable-3

4. Now, cherry-pick PR Update Readme to match the template #767 contents into that branch:

   $ git cherry-pick -x fdb8af7ca9dc96a426cc0ff977119676dad1aff8

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

   $ git cherry-pick -m1 -x fdb8af7ca9dc96a426cc0ff977119676dad1aff8

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update Readme to match the template #767 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-3/fdb8af7ca9dc96a426cc0ff977119676dad1aff8/pr-767

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.

[patchback]

Backport to stable-5: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-5/fdb8af7ca9dc96a426cc0ff977119676dad1aff8/pr-767

Backported as #819

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

[yurnov]

Backport to stable-3 created as #822 due to merge conflict