DEVPROD-3580: Add gateway api support

[pbhardwaj6]

Pull request description

This change is because of nginx is going out of support in march. Ref: https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/

Summary

• Adds Gateway API (HTTPRoute) support to Data Center product charts while preserving existing Ingress support.
• Updates functional test harness (KinD + MicroShift/CRC GitHub Actions) to run Gateway API-only (removes ingress-nginx dependency) and verifies app readiness via Envoy Gateway + port-forward.

Key Changes

• Helm charts (Bamboo/Bitbucket/Confluence/Crowd/Jira)

  • Adds new gateway: values block (disabled by default) and a new templates/httproute.yaml.
  • Enforces mutual exclusion: gateway.create cannot be enabled with ingress.create.
  • Updates proxy/base URL behavior to work for both Ingress and Gateway:
    • Uses gateway.hostnames[0] / gateway.https when Gateway is enabled.
    • Fixes Bitbucket SETUP_BASEURL generation to not accidentally use ingress.port in Gateway mode.
  • Updates NOTES.txt output to show the correct service URL for Gateway usage (including Crowd path handling and Bitbucket Mesh URL scheme).

• Functional tests / CI

  • KinD: installs Gateway API CRDs + Envoy Gateway, creates a test Gateway (atlassian-gateway), and removes ingress-nginx install.
  • MicroShift/CRC workflow: now also installs Gateway API CRDs + Envoy Gateway + GatewayClass + Gateway so tests don’t rely on pre-existing cluster state.
  • Introduces verify_gateway_ingress() that:
    • Port-forwards the Envoy proxy service
    • Uses curl with Host: header from the HTTPRoute
  • Adds/extends Gateway-focused harness validation (verify_gateway) and a Java chart rendering test for Gateway resources (GatewayTest).

• How It Works (Gateway Mode)

  • Gateway API controller is assumed/provisioned (tests install Envoy Gateway).
  • Charts create an HTTPRoute that attaches to an existing Gateway via:
    • gateway.gatewayName (required)
    • gateway.hostnames[] (required)
    • optional gateway.gatewayNamespace, gateway.path, gateway.pathType, etc.

Testing Notes

• Local chart rendering/unit test coverage
• KinD functional test (Gateway-only)

Checklist

• I have added unit tests
• I have applied the change to all applicable products
• The E2E test has passed (use e2e label)

---

Rovo Dev couldn't review this pull request
Upgrade to Rovo Dev Standard to continue using code review.

[nanux]

@pbhardwaj6 this is fairly large PR (46 files), can you please supply PR description and testing notes?

[amierzwicki]

It probably would be wise to also check that product route is at the position 1 - just to eliminate case where we accidentally override product route instead of prepending it with synchrony route.

[pbhardwaj6]

ok, will do the update

[amierzwicki]

Nice work! I've left few suggestions. We need to get the tests passing on this one.