fix(init): #1049 fix problem that kms-key ref picks wrong metadata.name

[haarchri]

Signed-off-by: haarchri chhaar30@googlemail.com

Description of your changes

• fixed following problem:

in kms alias:cannot create Alias in AWS: NotFoundException: Invalid keyId my-key
in rds dbcluster: KMSKeyNotAccessibleFault: The specified KMS key [rg-test-cluster-5bp8r-zzp65] does not exist, is not enabled or you do not have permissions to access it.

Fixes #902 #1049

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

created in one shot:

 apiVersion: kms.aws.crossplane.io/v1alpha1
 kind: Key
 metadata:
     name: my-key
 spec:
     deletionPolicy: Delete
     forProvider:
         region: us-west-2
         pendingWindowInDays: 21 
         tags:
         - tagKey: app
           tagValue: test
     providerConfigRef:
         name: example
---
apiVersion: kms.aws.crossplane.io/v1alpha1
kind: Alias
metadata:
    name: my-test
spec:
    deletionPolicy: Delete
    forProvider:
        region: us-west-2
        targetKeyIdRef:
            name: my-key
    providerConfigRef:
        name: example

NAME                                  READY   SYNCED   EXTERNAL-NAME
alias.kms.aws.crossplane.io/my-test   True    True     my-test

NAME                                READY   SYNCED   EXTERNAL-NAME
key.kms.aws.crossplane.io/my-key    True    True     34bf6b70-acc2-4bd0-80a0-184dbdf971d8

[haarchri]

e2e-test was failing because of #1052

[muvaf]

Thanks!