chore: remove track-prs for release project

[carolinaecalderon]

Ticket

Description

Remove the "wait-for-checks" step in the auto-backport workflow.
Remove references & functionality to track PRs for the release party process -- this should be part of the a greater discussion if we want to track tickets in Github or JIRA, and new scripts should be written accordingly.

Test Plan

n/a

Checklist

• Changes have been manually QA'd
• New features have been approved by the corresponding PM
• User-facing API changes have the "User-facing API Change" label
• Release notes have been added as a separate file under docs/release-notes/
  See Release Note for details.
• Licenses have been included for new code which was copied and/or modified from any external code

[netlify]

✅ Deploy Preview for determined-ui canceled.

Name	Link
🔨 Latest commit	e962b2c
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/6728edf9a32c44000825c33e

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.33%. Comparing base (f02872a) to head (e962b2c).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10170      +/-   ##
==========================================
- Coverage   54.35%   54.33%   -0.03%     
==========================================
  Files        1259     1259              
  Lines      157337   157337              
  Branches     3645     3645              
==========================================
- Hits        85526    85490      -36     
- Misses      71678    71714      +36     
  Partials      133      133              

Flag	Coverage Δ
backend	46.10% <ø> (-0.07%)	⬇️
harness	71.14% <ø> (ø)
web	54.30% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 5 files with indirect coverage changes

[davidfluck-hpe]

This looks good; I just had two nitpicky style/spacing things. I will point out, though, that track-pr does rely on some rph functionality that doesn't run anymore as part of release cutting, like creating the new Next release GitHub project and such. I did that manually this time, but that's part of the rph/Casper stuff that doesn't run anymore, so be aware of that.

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @jgongd on file. In order for us to review and merge your code, please start the CLA process at https://determined.ai/cla.

After we approve your CLA, we will update the contributors list (private) and comment @cla-bot[bot] check to rerun the check.

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @jgongd on file. In order for us to review and merge your code, please start the CLA process at https://determined.ai/cla.

After we approve your CLA, we will update the contributors list (private) and comment @cla-bot[bot] check to rerun the check.