Helm OCI Virtual repository allows for adding legacy and helm-oci repos

[alecchoy-vendor-jfrog]

Describe the bug
A clear and concise description of what the bug is.
Currently, the helm OCI virtual repository creation allows for adding both legacy aand helm-oci repos, which leads to failures resolving artifacts.

Requirements for and issue

• The helm OCI virtual repository creation allows for adding both legacy aand helm-oci repos, which leads to failures resolving artifacts.
• resource "artifactory_virtual_helmoci_repository" "helm-oci" { key = "helm-oci" repositories = ["helm-local", "helm-kubecost", "helm-elastic", "helm-astronomer", "helm-nonpipeline-local", "helm-prometheus", "helm-appdynamics", "helm-kedacore", "helm-ingress-nginx", "helm-prometheus-msteams", "helm-hashicorp", "helm-metricbeat", "helm-influx", "helm-fluent", "helm-external-dns"] default_deployment_repo = "helm-local" artifactory_requests_can_retrieve_remote_artifacts = true }
• Artifactory Cloud
• Latest
• Latest
• E+
• Cloud
• SF CASE 377538

Expected behavior
An error to be thrown when attempting to add a legacy helm local/remote repo in an OCI helm virtual repo.