Fix changlogs, remove PR reference

[emmyoop]

resolves #

Problem

A Dependency changelog referenced an Issue instead of a PR. This caused changelog generation to fail because the PR tag was missing but required.

Solution

Since GitHub treats PRs and Issue as the same thing, I removed all references to PR and only use Issue in the yaml files. The links will still build correctly because issues and prs are the same thing under the hood for GitHub.

I also updated the bot changelog to use Issue instead of PR in the yaml it auto generates.

This was tested by locally running the changie batch commands to ensure changelogs can be generated.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
• This PR includes type annotations for new and modified functions

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.09%. Comparing base (a1f0057) to head (1112fae).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9887      +/-   ##
==========================================
- Coverage   88.14%   88.09%   -0.05%     
==========================================
  Files         178      178              
  Lines       22455    22455              
==========================================
- Hits        19793    19782      -11     
- Misses       2662     2673      +11     

Flag	Coverage Δ
integration	85.46% <ø> (-0.13%)	⬇️
unit	61.87% <ø> (ø)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

The backport to 1.7.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.7.latest 1.7.latest
# Navigate to the new working tree
cd .worktrees/backport-1.7.latest
# Create a new branch
git switch --create backport-9887-to-1.7.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b44c2e498dfd634a3b4a51f4441afce5a3c7e8c7
# Push it to GitHub
git push --set-upstream origin backport-9887-to-1.7.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.7.latest

Then, create a pull request where the base branch is 1.7.latest and the compare/head branch is backport-9887-to-1.7.latest.