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

I'm opening this issue as a follow-up to #42246, and to expand on the discussion in https://github.com/Automattic/studio/issues/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.