add primary key version

[modular-magician]

Fixes #5688

Add primary version attribute for crypto key resource as per https://cloud.google.com/kms/docs/reference/rest/v1/projects.locations.keyRings.cryptoKeys

Note: This only adds the name and status attributes of the version object, not the complete version object, as my thinking was that these attributes are unlikely to be used and add unnecessary clutter, but I'm open to input on this.

Allows primary version attributes to be referenced as an attribute of the crypto key as

resource "google_kms_crypto_key" "example-key" {
  name            = "crypto-key-example"
  key_ring        = <some keyring>
}

output "key_primary_version_name" {
  value = google_kms_crypto_key.example-key.primary[0].name
}

output "key_primary_version_state" {
  value = google_kms_crypto_key.example-key.primary[0].state
}

Release Note Template for Downstream PRs (will be copied)

Add output-only `primary` version attribute to `google_kms_crypto_key` resource

Derived from GoogleCloudPlatform/magic-modules#9651

[lopezvit]

I think that this could be used to solve #16738 if it would be added to the data resource as well.
I have a question, is this checked with every execution as with the data resources? If the primary version is changed externally, would this be updated?

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.