fix(artifact-registry): fix a move issue with tf>1.7

[NitriKx]

Happy to be the first one to complain 🙂

As mentionned by @juliocc in #2606 the move is failing if we transfer the resource to the non-beta provider:

│ The "google_artifact_registry_repository_iam_binding" resource type does
│ not support moving resource state across resource types.

The TF 1.8 has introduced a new feature that makes the move failing (I was testing with 1.7 in #2606):

Providers can now transfer the ownership of a remote object between resources of different types, for situations where there are two different resource types that represent the same remote object type.
This extends the moved block behavior to support moving between two resources of different types only if the provider for the target resource type declares that it can convert from the source resource type. Refer to provider documentation for details on which pairs of resource types are supported.
https://github.com/hashicorp/terraform/blob/v1.8/CHANGELOG.md#180-april-10-2024

---

Checklist

I applicable, I acknowledge that I have:

• Read the contributing guide
• Ran terraform fmt on all modified files
• Regenerated the relevant README.md files using tools/tfdoc.py
• Made sure all relevant tests pass

[juliocc]

I won't say "I told you" ;)