Add support for Security Group Adoption (#165)

Issue #, if available: aws-controllers-k8s/community#1946

Description of changes:

The existing logic doesn't allow for adoption of existing SecurityGroups because spec.Name is a required property for creation but the aws SDK returns GroupName. The deepCopy in sdkFind then is not enough because of the different names. 
By copying SecurityGroup GroupName into spec.Name as part of the sdk_read_many_post_set_output we solve this issue.

This fix allows adoption of existing security groups. Tests have been successful in at least two test scenarios: adopting an existing SG and then modifying its properties, trying to adopt an invalid SG.
I've also ran a few additional tests with the modified controller to be sure that existing functionality didn't break:
* Create a new SG
* Modify this SG
* Delete this SG


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

Author: pcolazurdo

apis/v1alpha1/ack-generate-metadata.yaml

@@ -1,8 +1,8 @@
 ack_generate_info:
-  build_date: "2024-01-03T22:47:06Z"
-  build_hash: 00e081fb541587f33970ad80c99f2ac02e9c2525
+  build_date: "2024-01-15T16:33:37Z"
+  build_hash: 3753ca3f6610172e9e652d6e5e62e0a05f2e639c
   go_version: go1.21.5
-  version: v0.28.0-8-g00e081f
+  version: v0.28.0-11-g3753ca3
 api_directory_checksum: 8b27f9e65dbad1f5f825c84d1dbe8fd333baf2a5
 api_version: v1alpha1
 aws_sdk_go_version: v1.44.93

pkg/resource/security_group/sdk.go

@@ -1,4 +1,8 @@
 	if found {
+
+	// Needed because SecurityGroups Name are held in GroupName property of the AWS resource
+        ko.Spec.Name = resp.SecurityGroups[0].GroupName
+
         rm.addRulesToSpec(ko, resp.SecurityGroups[0])
     	
         // A ReadOne call for SecurityGroup Rules (NOT SecurityGroups)
@@ -8,4 +12,4 @@
 	    } else {
 		    ko.Status.Rules = rules
 	    }
-    }
+    }