Add mention about when to merge release PR

[carbolymer]

Changelog

- description: |
    Add mention about when to merge release PR.
    Move tagging section after CHaPing.
    Add build badges to README.md
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
   - documentation  # change in code docs, haddocks...

Context

Rendered:

• https://github.com/IntersectMBO/cardano-api/blob/mgalazyn/doc/add-tips-to-releasing-doc/RELEASING.md
• https://github.com/IntersectMBO/cardano-api/blob/mgalazyn/doc/add-tips-to-releasing-doc/README.md

Checklist

• [ ] Commit sequence broadly makes sense and commits have useful messages
• [ ] New tests are added if needed and existing tests are updated. See Running tests for more details
• [ ] Self-reviewed the diff

[palas]

FYI: Because we now enforce the use of cabal-gild to format cabal files and, in order to reduce the amount of hassle, I have cherry-picked the appropriate commit into your PR. This will make the cabal-gild CI check pass for the PR. The commit should be discarded automatically as soon as you either rebase or merge the PR (since it is already in the main branch). Feel free to discard it if you want, but that will make the new required action to fail until you rebase.

[palas]

FYI: I have rebased your branch because we have done changes to the formatting. I have made a copy of the unrebased branch here: backup/mgalazyn/doc/add-tips-to-releasing-doc