Re-instate an updated "Needs: Review Assignee" Bot

[jimchamp]

@mekarpeles writes

We used to have a bot to detect issues that may have been abandoned. I [@mekarpeles] do think having some workflow to detect abandoned issues is important. But the workflow needs to be updated to avoid infinite loops as there are lots of valid reasons a contributor may be stalled, including staff being the blockers.

If an issue is blocked by staff, we should add Needs: Staff / Internal Reviewed a PR but don't have merge powers? Use this. and exclude this label from future checks. If a contributor simply needs more time and is actively working on an issue, staff (while reviewing) can apply State: Work In Progress This issue is being actively worked on. [managed] and we can exclude this tag from future checks.

Otherwise, the stale_assignee bot should just add the label Needs: Review Assignee Issues that may have been abandoned by assignees and the lead should review. We might also add Needs: Response since we already have a workflow for this and it's one less additional query.

Original Question

Should we re-enable the stale_assignees_digest? What is preventing us from doing so? What issues should be labeled no-automation?

Stakeholders