[DOC] Updates for 2.8 and 2.9 patches rel notes

[knylander-grafana]

What this PR does:

Updates the 2.8 and 2.9 release notes with the latest changes for 2.8.3 and 2.9.1.

2.9.1: #6245
2.8.3: #6247

Which issue(s) this PR fixes:
Fixes #

Checklist

• Tests updated
• Documentation added
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[github-actions]

💻 Deploy preview deleted ([DOC] Updates for 2.8 and 2.9 patches rel notes).

[ie-pham]

not sure if you want this one reviewed or the other one so doing both

[knylander-grafana]

@ie-pham Thank you for identifying the missing CVEs. I've updated the entries to include those changes. Ready for review again.

[knylander-grafana]

Change committed. We should be good for another review.

[tempo-ci-app]

The backport to release-v2.9 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 branch
git switch --create backport-6248-to-release-v2.9 origin/release-v2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 78d413589889e2357697deca8c2f1e96287d48f7

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-6248-to-release-v2.9
# Create the PR body template
PR_BODY=$(gh pr view 6248 --json body --template 'Backport 78d413589889e2357697deca8c2f1e96287d48f7 from #6248{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release-v2.9] [DOC] Updates for 2.8 and 2.9 patches rel notes' --body-file - --label 'type/docs' --label 'backport' --base release-v2.9 --milestone release-v2.9 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-6248-to-release-v2.9

# Create a pull request where the `base` branch is `release-v2.9` and the `compare`/`head` branch is `backport-6248-to-release-v2.9`.

# Remove the local backport branch
git switch main
git branch -D backport-6248-to-release-v2.9

[tempo-ci-app]

The backport to release-v2.10 failed:

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

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-6248-to-release-v2.10 origin/release-v2.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 78d413589889e2357697deca8c2f1e96287d48f7

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-6248-to-release-v2.10
# Create the PR body template
PR_BODY=$(gh pr view 6248 --json body --template 'Backport 78d413589889e2357697deca8c2f1e96287d48f7 from #6248{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release-v2.10] [DOC] Updates for 2.8 and 2.9 patches rel notes' --body-file - --label 'type/docs' --label 'backport' --base release-v2.10 --milestone release-v2.10 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-6248-to-release-v2.10

# Create a pull request where the `base` branch is `release-v2.10` and the `compare`/`head` branch is `backport-6248-to-release-v2.10`.

# Remove the local backport branch
git switch main
git branch -D backport-6248-to-release-v2.10