docs(config options): rewrite allowedVersions

[HonkingGoose]

Changes

• Rewrite allowedVersions config option docs:
  • Use headings to separate different concepts/features
  • Focus on the reader, use words like you to draw the reader in
  • Hammer home the key point that you must begin and end your regex with the / character
  • Use the word must when a user must do something
  • Be clear about who does what

Context

Inspired by a user having problems with their regex in this discussion:

• Configure to skip some versions #29013

I read the allowedVersions docs to try to help the user figure out what's wrong. I missed the key point about the / character in the regex when skimming the docs. If I'm reading past it, what hope do regular users have... 🙃

I'm rewriting the docs to make it easier to skim, and hammer home the key points. 😄

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[renovate-release]

🎉 This PR is included in version 37.357.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.357.0

Your semantic-release bot 📦🚀