Release 2.8.2 - Githubissues

Fix #3756

patch release

Skipped, backport for previous release, not adding new versions that weren't already in 2.8

[ ] check the testing workflow (.github/workflows/test.yaml) and ensure that all matrix versions (.github/workflows/e2e.yaml and .github/workflows/release.yaml) are up to date for various component releases. If there have been any new releases (major, minor or patch) of those components since the latest version seen in that configuration make sure the new versions get added before proceeding with the release. Remove any versions that are no longer supported by the environment provider.
[ ] Kubernetes (via KIND and the latest image available when creating a new rapid channel cluster from the GKE new cluster wizard)
[ ] Istio (via Istio's releases page)

KIC version bump only for older release backport

[ ] Note: it might be possible that the latest Gateway version is not compatible with KIC and code changes are required. In such case, a decision whether to release with no compliance with the latest Gateway version should be made on a team level.
[ ] Check the latest minor Kong Gateway release in Kong releases.
[x] Make sure the image tag in config/image/enterprise/kustomization.yaml, config/image/oss/kustomization.yaml, and config/variants/enterprise/kustomization.yaml is updated accordingly.
[x] Run make manifests to regenerate manifests using the modified kustomizations and open a PR with the changes (similarly to this PR).

No FOSSA update, we don't scan non-main branches

[x] ensure that you have up to date copy of main: git checkout main; git pull
[x] create the release branch for the version (e.g. release/1.3.1): git branch -m release/x.y.z
[x] Make any final adjustments to CHANGELOG.md. Double-check that dates are correct, that link anchors point to the correct header, and that you've included a link to the Github compare link at the end.
[ ] Resolve all licensing issues that FOSSA has detected. Go to Issues tab in FOSSA's KIC project and resolve every issue, inspecting if it's a false positive or not. ignored.go script should be useful to look for issues that have been already resolved and reappeared due to version changes.
[ ] Update ignored.json following instructions in README.
[ ] Retrieve the latest license report from FOSSA and save it to LICENSES (go to Reports tab in FOSSA's KIC project, select 'plain text' format, tick 'direct dependencies' and download it).
[x] ensure base manifest versions use the new version (config/image/enterprise/kustomization.yaml and config/image/oss/kustomization.yaml) and update manifest files: make manifests
[x] push the branch up to the remote: git push --set-upstream origin release/x.y.z

[x] Check the latest test run to confirm that E2E tests are succeeding. If you are backporting features into a non-main branch, run a targeted E2E job against that branch.
[x] Open a PR from your branch to main.
[ ] Once the PR is merged, initiate a release job. Your tag must use vX.Y.Z format. Set latest to true if this will be the latest release.
[ ] CI will validate the requested version, build and push an image, and run tests against the image before finally creating a tag and publishing a release. If tests fail, CI will push the image but not the tag or release. Investigate the failure, correct it as needed, and start a new release job.

Kong / kubernetes-ingress-controller