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,5 +1,5 @@
 ack_generate_info:
-  build_date: "2024-09-12T18:02:26Z"
+  build_date: "2024-09-17T17:43:02Z"
   build_hash: f8f98563404066ac3340db0a049d2e530e5c51cc
   go_version: go1.22.6
   version: v0.38.1

templates/hooks/route_table/sdk_read_many_post_set_output.go.tpl

@@ -8,7 +8,7 @@
 		// then assign resource's tags to maintain tag order
 		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
@@ -20,4 +20,5 @@
 			ko.Spec.Routes[i].VPCEndpointID = route.GatewayID
 			ko.Spec.Routes[i].GatewayID = nil
 		}
-	}
+	}
+