Issue/PR Wrangler Role

[adambkaplan]

The Envoy project shared many of what they consider best practices for open source projects at Maintainer Summit. One practice Shipwright should adopt is the "Issue/PR Wrangler" role.

This is a weekly "on call" rotation, where the assignee is in charge of the following:

1. Triaging new pull requests such that they are assigned to an approver with subject matter expertise.
2. Review new GitHub issues and either (a) accept them to the backlog, (b) tag a relevant expert for backlog acceptance, or (c) close them with an appropriate comment.
3. Re-run flaky tests on open PRs.
4. Approve CI test runs from new participants.

An important aspect of this role is that the individual is NOT responsible for approving PRs. Their job is to "keep the project moving."

I think this will help us be more "async oriented," and remove the need for folks to ask for PR reviews during the weekly community meeting. Thoughts?