Post PBB migration: Refactor "Pull Request Trigger" workflow

[t-will-gillis]

Overview

The new Projects Beta is structured a little differently from Projects (classic). During to our recent migration from Projects (classic) to Projects Beta, we scrubbed our workflows and removed all functionality that referenced 'columns' as this term is no longer used. We need to refactor our post migration workflows so that they have similar functionality as previously.

Details

Prior to the migration to Projects Beta, pull-request-trigger.yml used a 3rd party automation that removed merged PRs and closed + unmerged PRs from the Project Board. This behavior needs to be replicated using GraphQL- if possible.

Action Items

Note that in Projects Beta, closed PRs are immediately archived.

• To confirm: Do we want to continue this behavior with Projects Beta?
• Determine whether GraphQL (or the REST API) is able to delete merged PRs and closed + unmerged PRs from the Project archives
• If so, implement this feature

Resources/Instructions

• Initial GraphQL queries and results
• GitHub GraphQL Explorer
• GitHub GraphQL API
• Hack for LAs GitHub Actions
• This issue initiated by Prep for Project Board Migration: GitHub Actions / Workflows Part 1 of 2  #6993

[t-will-gillis]

This issue is not needed: Projects Beta has an automatic workflow that archives merged and closed PRs.