unified composition names

[nimakaviani]

we have networks.awsblueprints.io/v1alpha1 for aws-provider compositions of VPC:

https://github.com/aws-samples/crossplane-aws-blueprints/blob/9197d704ea8f55621aac4422bd166d6e3c44b583/compositions/aws-provider/vpc/vpc-xrd.yaml#L9-L18

and vpc.awsblueprints.io/v1beta1 for aws-jet-provider compositions of VPC:

https://github.com/aws-samples/crossplane-aws-blueprints/blob/9197d704ea8f55621aac4422bd166d6e3c44b583/compositions/terrajet-aws-provider/vpc/vpc-xrd.yaml#L10-L15

both refer to the same resource but capturing different spec representation of it. does it make sense to settle on something like the following for better naming conventions?

networks.awsblueprints.io/v1alpha1 for aws-provider and
networks.awsblueprints.io/v2alpha1 for aws-jet-provider

or even easier

networks.awsblueprints.io/v1 for aws-provider and
networks.awsblueprints.io/v2 for aws-jet-provider

after all these are samples, so versioning is less relevant. but naming inconsistencies could be confusing. thoughts?