Adding dependabot PR number to dependabot issue title for title uniqueness and automated closeability

[DavidMcClatchey]

BACKEND PULL REQUEST

Related Issue

• Dependabot failing to close associate issues. #8454

Changes Proposed

• This adds the dependabot PR number to the dependabot issue title so that a unique result comes back when querying for the issue associated with the PR. With only one dependabot issue result coming back, the issue tied to the PR should now be closeable within the dependabotClosePRIssue.yml.

Testing

• I tested this by first manually updating the title of Dependabot PR #8442 Bump the storybook group in /frontend with 13 updates opened #8443 via adding the associated PR number 8442 so that the issue title would reflect what it would look like if the new dependabotCreatePRIssue.yml had created it. Then I ran the gh commands for closing the issue from my local computer.
• If you would like to test, you can find a dependabot issue that should have been closed and follow the same process.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[emyl3]

Tested this locally as well using this PR #6919 -- works as you described

When merged in, we would have to manually close the currently open dependabot PRs or update the titles for this to work right? 🤔

[DavidMcClatchey]

Tested this locally as well using this PR #6919 -- works as you described

When merged in, we would have to manually close the currently open dependabot PRs or update the titles for this to work right? 🤔

Good call, yea this solution only applies to dependabot PRs created after this gets merged, so for any currently open dependabot PRs that never get merged but get superseded by another dependabot PR we'd have to manually close their associated issues or update the titles like you suggested. I think updating the titles is a good idea so we don't have to keep tabs on what gets superseded. I'll add that scenario/process to the cleanup spike!

[DavidMcClatchey]

Tested this locally as well using this PR #6919 -- works as you described
When merged in, we would have to manually close the currently open dependabot PRs or update the titles for this to work right? 🤔

Good call, yea this solution only applies to dependabot PRs created after this gets merged, so for any currently open dependabot PRs that never get merged but get superseded by another dependabot PR we'd have to manually close their associated issues or update the titles like you suggested. I think updating the titles is a good idea so we don't have to keep tabs on what gets superseded. I'll add that scenario/process to the cleanup spike!

Edit: I just realized Github's definition of "closed" is also when a PR gets merged and not just when it's closed closed without merging. So, the scenario would apply to dependabot PRs that get merged after this PR gets merged as well. In light of that, I'll just manually modify issue titles once this is merged in since the issue renaming will need a quickish turnaround.
Extra edit: @emyl3 was fully correct and this was just me working through it in public 😅

[mpbrown]

Tested it with #7555 and everything looks good!