chore: add labels for a clear reproductive steps flow

Start with the issue's three requirements: define the reproductive-steps flow chart, identify the labels needed to support it, and determine the scope of the waiting-for-response bot. Done means the flow is documented, the supporting labels are specified, and the bot behavior or a separate task for it is clearly defined.

Description

Cross posting from internal conversations:

As a side note, it would be ideal if we add a tag named something like needs reproductive confirmation or similar where the description is: The issue needs confirmation from developers that it has been reproduced .

---

Looking into the future we should do something like:

• Check if the issue has reproductive and clear reproductive steps:
  • Add the "has reproductive steps" label if it has together with "needs reproductive confirmation"
  • Add the "needs reproductive steps" label if it has not
• Check those "has reproductive steps" issues can be reproduced
  • Add the "has been reproduced" if it was reproduced with a comment that details the steps and any additional context to reproduce
  • Add the "could not be reproduced" if it was not reproduced with a comment that details at what step the reproductive steps could not be followed together with the "waiting for response" label
  • If the "waiting for response" label persists for 2 weeks without any updated to comments we would have the BOT close the issue with a message along the lines of: ""Hey since this seems to be silent for a while, I am closing this for now. If anything comes up, don't hesitate on telling." (Credits to Renan, he usually used this as a template for his replies and I liked it and started using it).

Requirements

• There is a defined flow chart explaining this flow
• There are labels to support the flow outlined in the flow chart
• There is a BOT that closes waiting for response issues (we could have a separate task for this effort if preferred)

Additional Context

No response