feat!(helm): Add installGatewayAPI helm chart value

[adleong]

We add a new value to the linkerd-crds Helm chart called installGatewayAPI which acts as a default value for enableHttpRoutes, enableTlsRoutes, and enableTcpRoutes. We also update the logic of the linkerd install and linkerd upgrade commands to set this installGatewayAPI value to true if there are any gateway API CRDs managed by Linkerd on the cluster and false otherwise. Users can still override this setting by specifying the --set installGatewayAPI=(false|true) flag.

This is all to move us toward the eventual goal of having the Gateway API CRDs treated as an external dependency rather than being managed by Linkerd without breaking the upgrade path.

[adleong]

This is blocked on #13741 because new installs no longer include the Gateway API CRDs. This is causing integration tests to fail because of the panic which is fixed in #13741

[alpeb]

While testing I see the helm chart installs by default the CRDs while the CLI doesn't. Is that expected?

$ bin/helm-build
$ helm template linkerd-crds charts/linkerd-crds | rg tlsroute
# Source: linkerd-crds/templates/gateway.networking.k8s.io_tlsroutes.yaml
  name: tlsroutes.gateway.networking.k8s.io
    kind: TLSRoute
--snip--
$ bin/linkerd install --crds | rg tlsroute
Rendering Linkerd CRDs...
Next, run `linkerd install | kubectl apply -f -` to install the control plane.
--empty--

[adleong]

@alpeb yes this is expected. In Helm's default mode, it doesn't differentiate between install and upgrade for template rendering, so in the short term we still include the gateway API CRDs by default. On the Linkerd CLI side, we can be more intelligent and skip the gateway API CRDs by default for new installs or for upgrades when the gateway API CRDs are not already installed by Linkerd.