Add check required crds

[u-kai]

What type of PR is this?
Feature

Which issue does this PR fix:
#660

What does this PR do / Why do we need it:
This PR adds a feature that pre-checks the required CRDs for the controller.
If the required CRDs are not installed, the controller will fail fast.

If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:

Testing done on this change:

Tested by deploying the changes in my EKS cluster.
If the required CRDs are not installed, the controller logs the following message:

{"level":"info","ts":"2025-01-01T04:23:53.272Z","caller":"workspace/main.go:161","msg":"log level set to debug"}
...
{"level":"info","ts":"2025-01-01T04:23:53.272Z","logger":"setup","caller":"runtime/proc.go:272","msg":"Webhook is enabled, 'webhook-cert' secret must contain a valid TLS key and cert"}
{"level":"fatal","ts":"2025-01-01T04:23:53.376Z","logger":"setup","caller":"runtime/proc.go:272","msg":"required CRDs check failed:missing required CRDs: gateway.networking.k8s.io/v1, Kind=Gateway, gateway.networking.k8s.io/v1, Kind=GatewayClass, gateway.networking.k8s.io/v1, Kind=HTTPRoute, gateway.networking.k8s.io/v1, Kind=GRPCRoute, gateway.networking.k8s.io/v1alpha2, Kind=TLSRoute"}

Automation added to e2e:

No
Will this PR introduce any new dependencies?:

No
Will this break upgrades or downgrades. Has updating a running cluster been tested?:

Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.