Remove status:ready label from repository, workflows, forms, and docs

[HonkingGoose]

Describe the proposed change(s).

If a user creates an Issue, it's automatically converted to a Discussion. The bug/feature is discussed, and when we have the requirements figured out, a maintainer creates a issue. This means that (in theory, at least) we should only have status:ready issues. This means that we can drop the status:ready label.

What about the other status:* labels?

We keep the status:requirements label in case we need to "cheat" to create Issues we know we need, but don't have the requiements figure out fully. This should be seen as an "escape hatch" though.

We keep the status:blocked label, to indicate issues that need some other thing first.

And finally, we also keep the status:in-progress label to indicate that we started work on the issue.

Todos:

• Drop status:ready mentions from developer docs
• Explain in developer docs that we should only create "issues that are actionable", if we don't already
• Drop status:ready from Issue Forms, Discussion Forms
• Drop status:ready from any bot/workflow configuration
• Check if everything keeps working
• Final stap: remove the actual status:ready label in the GitHub UI

[renovate-release]

🎉 This issue has been resolved in version 37.6.2 🎉

The release is available on:

• GitHub release
• 37.6.2

Your semantic-release bot 📦🚀