Bump Gateway API to 1.4.1

[sunjayBhatia]

No description provided.

[sunjayBhatia]

supercedes #7265

[dprotaso]

@sunjayBhatia gateway API 1.5 is out - does it make sense to jump to that?

[sunjayBhatia]

@sunjayBhatia gateway API 1.5 is out - does it make sense to jump to that?

I was thinking of doing an intermediate release of contour to get up to speed w/ 1.4.x to do a smooth upgrade/deprecation of e.g. BackendTLSPolicy v1alpha3 in a further release where we bump to 1.5.x, playing catch up a bit

[dprotaso]

cool sounds good

[codecov]

Codecov Report

❌ Patch coverage is 93.75000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 81.82%. Comparing base (8f18e9f) to head (c7e6a7b).
⚠️ Report is 28 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/gatewayapi/listeners.go	50.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7473      +/-   ##
==========================================
- Coverage   81.84%   81.82%   -0.03%     
==========================================
  Files         130      130              
  Lines       15722    15722              
==========================================
- Hits        12868    12864       -4     
  Misses       2571     2571              
- Partials      283      287       +4     

Files with missing lines	Coverage Δ
internal/dag/cache.go	96.98% <100.00%> (ø)
internal/dag/gatewayapi_processor.go	93.86% <100.00%> (ø)
internal/provisioner/controller/gatewayclass.go	71.13% <ø> (ø)
internal/status/backendtlspolicyconditions.go	86.20% <100.00%> (-5.18%)	⬇️
internal/gatewayapi/listeners.go	99.03% <50.00%> (-0.97%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 60d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Ensure your PR is passing all CI checks. PRs that are fully green are more likely to be reviewed. If you are having trouble with CI checks, reach out to the #contour channel in the Kubernetes Slack workspace.
• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack