[VETS-API] [DISCOVERY] Iterate on Current Backend CI Checks

[ryan-mcneil]

Issue Description

There are currently several issues with the GHAs that are attempting to simplify the lives of the BE CoP when it comes to approving PRs, but instead have had some unintended effects that are blocking/slowing development, raising a ton of noise, and adding to our workload. I believe we need to to step back and establish what we're trying to accomplish, what we have that's working, what doesn't work, and what needs to be put in place to achieve our ideal workflow.

---

Tasks

• Establish explicit criteria for PR approval
• Whiteboard ideal process with edge cases
  • failing specs
  • updating to master
  • re-approvals
  • approvals required by multiple teams
  • teams exempt from backend approval (Mobile, Identity, Lighthouse?)
• Consider options for workflows to meet these requirements, regardless of what is already in place
  • Determine if any existing checks can be used or easily modified to meet these
• Discuss options with CoP
• Create tickets for follow up work

Acceptance Criteria

• Confluence page is created with whiteboard and decisions documented
• Tickets created

[ryan-mcneil]

Confluence Doc with Whiteboard: https://vfs.atlassian.net/wiki/spaces/PRT/pages/3535470594/Vets+API+CI+Backend+approval+Consolidation

[ryan-mcneil]

Next ticket: #95609