Spike: Investigate ways to allow single approval of copilot authored PRs

Look at ways to assign issues to copilot that only require a single dev review the PR.
This might include branch policy changes and issue or pr automation.

Currently, when an issue is assigned to copilot by team member 1, when team member 2 reviews the PR and adds a suggestion, then neither 1 or 2 are valid reviewers, so the PR has to be approved by a third team member.

If we had an external, untrusted contributor work on the issue, only 2 team members would be required given the same suggestions, approvals, etc.

Working with copilot shouldn't be more burdensome than working with external contributors.