fix(translator): check gateway class and do not skip listeners when gateway class is not managed by KIC

[randmonkey]

What this PR does / why we need it:

Do not skip checking certificates in gateway listeners that does not has "Programmed" condition if the GatewayClass is not managed by KIC. The change fixes an issue when KIC is deployed by gateway operator, certificates gets deleted when dataplane (Kong gateway) pods are changed.

Which issue this PR fixes:

fixes #7660 (then also Kong/kong-operator#1769)

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

• the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

[codecov]

Codecov Report

❌ Patch coverage is 80.43478% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 77.2%. Comparing base (5eea70b) to head (1aca435).
⚠️ Report is 14 commits behind head on main.

Files with missing lines	Patch %	Lines
...nal/controllers/gateway/gatewayclass_controller.go	20.0%	3 Missing and 1 partial ⚠️
internal/store/store.go	66.6%	2 Missing and 1 partial ⚠️
internal/dataplane/translator/translate_certs.go	88.2%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #7666   +/-   ##
=====================================
  Coverage   77.2%   77.2%           
=====================================
  Files        222     222           
  Lines      25870   25903   +33     
=====================================
+ Hits       19994   20020   +26     
  Misses      4849    4849           
- Partials    1027    1034    +7     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[team-k8s-bot]

The backport to release/3.4.x 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-release/3.4.x release/3.4.x
# Navigate to the new working tree
cd .worktrees/backport-release/3.4.x
# Create a new branch
git switch --create backport-7666-to-release/3.4.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 25626627e3c762ac3cc12a0637b5802126b913be
# Push it to GitHub
git push --set-upstream origin backport-7666-to-release/3.4.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.4.x

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

[team-k8s-bot]

The backport to release/2.12.x 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-release/2.12.x release/2.12.x
# Navigate to the new working tree
cd .worktrees/backport-release/2.12.x
# Create a new branch
git switch --create backport-7666-to-release/2.12.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 25626627e3c762ac3cc12a0637b5802126b913be
# Push it to GitHub
git push --set-upstream origin backport-7666-to-release/2.12.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/2.12.x

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