Add support to provision Gateway on Helm install

[ciarams87]

Proposed changes

Problem: As a user of NGF, I would like to be able to deploy a Gateway resource as part of my Helm installation

Solution: Add support for creating a Gateway resource as part of a Helm install.

Testing: Tested locally installing various Gateway configurations using Helm

Closes #1533

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Release notes

If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.

Added support to provision a Gateway resource as part of a Helm install.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.71%. Comparing base (f33db51) to head (482f7bc).
Report is 137 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1623      +/-   ##
==========================================
+ Coverage   85.67%   85.71%   +0.03%     
==========================================
  Files          83       83              
  Lines        5181     5181              
==========================================
+ Hits         4439     4441       +2     
+ Misses        690      689       -1     
+ Partials       52       51       -1     

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

[pleshakov]

I wonder why can't we just include listeners as we include ports here

nginx-gateway-fabric/deploy/helm-chart/values.yaml

Lines 128 to 136 in f33db51

	ports:
	- port: 80
	targetPort: 80
	protocol: TCP
	name: http
	- port: 443
	targetPort: 443
	protocol: TCP
	name: https

? What's the value of defining the fields of listeners?

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[salonichf5]

LGTM, is there conformance tests we can enable for this?