Send a notification to "All activity" watchers when a draft pull request is marked ready for review

[native-api]

Select Topic Area

Product Feedback

Body

From https://github.com/orgs/community/discussions/22826

Currently, if I watch a repository with "All activity" option, I get notifications on all the activity in a pull request -- except changing pull requests's draft status.
And there's no way to enable being notified of this in watch settings.
While the name "All activity" suggests that there should not be any surprising and hard-coded omissions, I should literally see everything happening, with no "if"s and "but"s.

In our project, this keeps causing huge, unnecessary delays in processing user-submitted pull requests, including time-sensitive ones (e.g. supporting a new release of an upstream product).

Following is a quote from my message in the above discussion:

As a team member, I am able to review any pull request, whether I'm assigned or not. Our project does not have tons of pull requests so it's not necessary to explicitly assign people to them to avoid duplication of effort. Moreover, even people not on the team can review -- their review will just be marked with a pale tick rather than a bright green tick and will not count if the repository is configured to require reviews before merging.

Not receiving notifications has repeatedly caused delays measured in days before a pull request that was submitted as draft is merged, for absolutely no good reason -- just because I have better things to do than checking on things manually every day.

So I see absolutely no reason to not send notifications. At the very least, this should be a configurable option among the other notification types.

Just now, I've learned by chance of configuring "code owners" who would supposedly get those notifications. But that's a hard-coded rather than user-configurable setting.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐