Repo Gardening: audit use of [Status] label in the action

[jeherve]

I'm opening this issue as a follow-up to #42246, and to expand on the discussion in Automattic/studio#1012

Since we’re transitioning to Linear, which handles status updates automatically, this behavior is no longer needed—it actually convolutes the status.
-- @richtabor

---

Our actions currently add the following [Status] labels to issues and PRs:

• [Status] Auto-allocated when an issue is automatically added to a Project Board (either The One Board or a Project Board used for a specific project or team)
• [Status] Stale when an issue has been opened for a long time (defined per repo) without any update.
• [Status] In Progress when a PR is opened in draft mode.
• [Status] Needs Author Reply when information is missing from a PR.
• [Status] Design Input Requested when a Slack message was sent to a Design team about a specific PR.
• [Status] Editorial Input Requested when a Slack message was sent to an editorial team about a specific PR.
• [Status] Priority Review Triggered when a Slack message was sent to developers about an important issue (i.e. high / blocker priority bug).
• [Status] Escalated to Product Ambassadors when a Slack message was sent to Product ambassadors about an important issue.

Some of those status labels are meant as an indicator for folks following the issue on GitHub. Some are also used as a way to ensure the action does not run twice and no Slack message is sent multiple times about the same issue.

If some of those labels cause confusion in Linear, we could consider renaming them to something else, or simply to remove or rename the [Status] prefix. @richtabor What do you think?

---

cc'ing @inaikem since we were discussing about the Linear transition yesterday.

[github-actions]

OpenAI suggested the following labels for this issue:

• [Feature Group] Other Infrastructure: This issue relates to the overall structure and processes of the repository's management, which falls under infrastructure.
• [Feature] Notifications: The concerns raised about status updates and labels are related to how notifications are communicated on GitHub.
• [Feature] Activity Log: Auditing and tracking the use of labels suggests a need for effective logging of actions taken on issues and PRs.

[github-actions]

This issue could use some more labels, to help prioritize and categorize our work. Could you please add at least a [Type], a [Feature], and a [Pri] label?