Default behavior on gateway(lattice service network) association to VPC

[liwenwu-amazon]

Change default behavior of gateway(lattice service network) association to VPC as follow

• if gateway do NOT have annotation application-networking.k8s.aws/lattice-vpc-association, the controller will try to associate this gateway to VPC

• if gateway have annotation, application-networking.k8s.aws/lattice-vpc-association: the controller will use its value to decide whether to associate

      * `application-networking.k8s.aws/lattice-vpc-association:false`   not to associate
      
      * `application-networking.k8s.aws/lattice-vpc-association: true`: associate to VPC
  

[liwenwu-amazon]

Here are some customer requests

What result did you expect to see and what was the actual result?*
I was trying section "Set up multi-cluster/multi-VPC service-to-service communications" in https://www.gateway-api-controller.eks.aws.dev/

Document has steps to export Kubernetes inventory-ver2 Service/HTTPRoute from EKS cluster 2 and import it to EKS cluster 1. I am not sure if this step sets up the VPC associations automatically - THAT DID NOT HAPPEN atleast for me and curl commands weren't working

Also the document doesn't prescribe to set up VPC associations manually from VPC Lattice console. I was able to make it work after associating the VPCs of 2 clusters manually via AWS Management/ VPC Lattice console.

Would be good to automate it when we perform export from cluster 2 and import to cluster 1. If this is not expected behavior, we need to have a step in document to elaborate on how to set up VPC associations manually via AWS Management /VPC Lattice console

Please specify the steps to reproduce the issue on our end
Elaborated above