Rewrite minimal reproduction guide to get to the point quicker

[HonkingGoose]

Describe the proposed change(s).

Rewrite the minimal reproduction guide ¹, so that users can get started creating the reproduction quicker:

• Refactor current docs with: docs: improve minimal reproductions guide #28926
• Move actionable information up front
• Move background info down
• Rewrite for simplicity:
  • Simpler words
  • Short sentences
  • Use lists if needed
  • Focus on the reader
  • Update links that point to minimal-reproductions.md

Footnotes

1. docs/development/minimal-reproductions.md ↩

[renovate-release]

🎉 This issue has been resolved in version 37.379.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[karlhorky]

@HonkingGoose Thanks for #29275 👍 nice improvements.

To make the guide even more approachable for contributors, I would suggest dropping + simplifying steps, including dropping the readme.md (the description should be in a discussion or issue anyway):

-1. Put your minimal reproduction repository on GitHub, only use GitLab or Bitbucket if needed
+1. Put your minimal reproduction repository on GitHub, only use GitLab or Bitbucket if needed (make sure the repo is public)
1. Use the fewest number of repository files and dependencies
1. Reduce your Renovate config to a minimum
1. Remove private or secret information
-1. Create a `readme.md` file that explains the _current behavior_ and _expected behavior_
-1. Set the repository visibility to `public`
-1. Give us the link to the repository

Also, for some first baby steps in the direction of a minimal reproduction template, I would add an example config link to step 3:

-1. Reduce your Renovate config to a minimum
+1. Reduce your Renovate config to a minimum (eg. [simple base config starter](https://example.com))

Then, if the idea of a minimum reproduction template is amenable to the Renovate team, this could be expanded to multiple GitHub repo templates - one for each for each package manager (eg. including an empty package.json for Node.js projects), to get closer to the "one-click starter" idea that I mentioned.

[rarkins]

I disagree about dropping the readme. In a large % of cases, reproduction repositories are not self-explanatory, even with the associated discussion