Route addition in routeTable changes CR spec

This fix accomodates an aws api bug so as to prevent routeTable CR spec
from changing.
Details explained in the issue description.

Author: Nishant Burte

apis/v1alpha1/ack-generate-metadata.yaml

@@ -1,13 +1,13 @@
 ack_generate_info:
-  build_date: "2023-12-12T12:34:35Z"
+  build_date: "2023-12-15T06:34:46Z"
   build_hash: 3653329ceeb20015851b8776a6061a3fb0ec2935
-  go_version: go1.21.0
-  version: "3653329"
+  go_version: go1.21.1
+  version: v0.27.1-6-g3653329
 api_directory_checksum: d452bf19bfd1496aacdc215bf7cc9ea86c55c122
 api_version: v1alpha1
 aws_sdk_go_version: v1.44.93
 generator_config_info:
-  file_checksum: df1057de840147701c11acfdbed0e28e9b0ddd96
+  file_checksum: 0ea278e11a33d237e88a1bcdca878656a8ba43f9
   original_file_name: generator.yaml
 last_modification:
   reason: API generation

pkg/resource/route_table/sdk.go

@@ -9,3 +9,15 @@
 		ko.Spec.Tags = r.ko.Spec.Tags
 	}
 
+	// Even if route is created with arguments as VPCEndpointID,
+	// when aws api is called to describe the route (inside skdFind), it
+	// returns VPCEndpointID as GatewayID. Due to this bug, spec section for
+	// routes is populated incorrectly in above auto-gen code.
+	// To solve this, if 'GatewayID' has prefix 'vpce-', then the entry is
+	// moved from 'GatewayID' to 'VPCEndpointID'.
+	for i, route := range ko.Spec.Routes {
+		if route.GatewayID != nil && strings.HasPrefix(*route.GatewayID, "vpce-") {
+			ko.Spec.Routes[i].VPCEndpointID = route.GatewayID
+			ko.Spec.Routes[i].GatewayID = nil
+		}
+	}