[query-frontend] Close response body in request handler

[flxbk]

What this PR does

This closes the response body received by the frontend handler to free the resources associated with it. If this isn't done and the response.Body contains a non-noop io.ReadCloser it causes a memory leak.

Which issue(s) this PR fixes or relates to

Fixes #

Checklist

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

[charleskorn]

[nit] This likely won't make much sense to an end-user. Perhaps something like "fix memory leak on every request" would be more appropriate?

[flxbk]

Absolutely, 5d8e8b0

[grafanabot]

The backport to r280 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-7654-to-r280 origin/r280
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x eaef37753546273732aa7fc3e10fc670d57a4963
# Push it to GitHub
git push --set-upstream origin backport-7654-to-r280
git switch main
# Remove the local backport branch
git branch -D backport-7654-to-r280

Then, create a pull request where the base branch is r280 and the compare/head branch is backport-7654-to-r280.

[grafanabot]

The backport to r279 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-7654-to-r279 origin/r279
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x eaef37753546273732aa7fc3e10fc670d57a4963
# Push it to GitHub
git push --set-upstream origin backport-7654-to-r279
git switch main
# Remove the local backport branch
git branch -D backport-7654-to-r279

Then, create a pull request where the base branch is r279 and the compare/head branch is backport-7654-to-r279.

[grafanabot]

The backport to r281 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-7654-to-r281 origin/r281
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x eaef37753546273732aa7fc3e10fc670d57a4963
# Push it to GitHub
git push --set-upstream origin backport-7654-to-r281
git switch main
# Remove the local backport branch
git branch -D backport-7654-to-r281

Then, create a pull request where the base branch is r281 and the compare/head branch is backport-7654-to-r281.

[grafanabot]

The backport to r282 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-7654-to-r282 origin/r282
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x eaef37753546273732aa7fc3e10fc670d57a4963
# Push it to GitHub
git push --set-upstream origin backport-7654-to-r282
git switch main
# Remove the local backport branch
git branch -D backport-7654-to-r282

Then, create a pull request where the base branch is r282 and the compare/head branch is backport-7654-to-r282.

[grafanabot]

The backport to release-2.12 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-7654-to-release-2.12 origin/release-2.12
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x eaef37753546273732aa7fc3e10fc670d57a4963
# Push it to GitHub
git push --set-upstream origin backport-7654-to-release-2.12
git switch main
# Remove the local backport branch
git branch -D backport-7654-to-release-2.12

Then, create a pull request where the base branch is release-2.12 and the compare/head branch is backport-7654-to-release-2.12.