Invalid annotation key for sigs.k8s.io/cluster-api-provider-aws/v2-last-applied-tags

[tmad]

/kind bug

What steps did you take and what happened:
Upgraded to v2.0.0 with clusterctl

Looked into cluster-api-provider-aws logs. There were issues like:
Invalid value: \"sigs.k8s.io/cluster-api-provider-aws/v2-last-applied-tags\" a qualified name must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName', or 'my.name', or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName')

Anything else you would like to add:
The issue is probably caused by two slashes appearing in the new annotations instead of one.
This may be appearing when using additionalTags.

• controllers/awsmachine_tags.go - TagsLastAppliedAnnotation = "sigs.k8s.io/cluster-api-provider-aws/v2-last-applied-tags"
• pkg/cloud/services/ec2/launchtemplate.go - TagsLastAppliedAnnotation = "sigs.k8s.io/cluster-api-provider-aws/v2-last-applied-tags"
• controllers/awsmachine_security_groups.go - SecurityGroupsLastAppliedAnnotation = "sigs.k8s.io/cluster-api-provider-aws/v2-last-applied-security-groups"

Environment:

• Cluster-api-provider-aws version: 2.00
• Kubernetes version: (use kubectl version): 1.23

[k8s-ci-robot]

@tmad: This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.