fix: handle uri skeleton non null

[acpana]

Today it seems that the ExpectedSkeleton is not checked if it is not null BUT the servicemappings lists idTemplateCanBeUsedToMatchResourceName == false . We should at least throw a warning in this scenario, otherwise the ExpectedSkeleton is not checked which may lead contributors to believe that their test is passing!

[acpana]

Example:

k8s-config-connector/config/servicemappings/vertexai.yaml

Lines 20 to 31 in 2f4f2c6

	spec:
	name: VertexAI
	version: v1beta1
	serviceHostName: "aiplatform.googleapis.com"
	resources:
	- name: google_vertex_ai_dataset
	kind: VertexAIDataset
	# This resource does not support import.
	skipImport: true
	idTemplate: "{{name}}"
	idTemplateCanBeUsedToMatchResourceName: false
	resourceAvailableInAssetInventory: true

But the ExpectedSkeleton is not null

k8s-config-connector/pkg/resourceskeleton/testdata/uri-skeleton.yaml

Lines 1114 to 1122 in 2f4f2c6

	- ExpectedSkeleton:
	apiVersion: vertexai.cnrm.cloud.google.com/v1beta1
	kind: VertexAIDataset
	spec:
	projectRef:
	external: kcc-test
	location: us-central1
	ResourceConfigId: VertexAIDataset
	URI: "https://us-central1-aiplatform.googleapis.com/v1beta1/projects/kcc-test/locations/us-central1/datasets/1234567890?alt=json"

This stood out to me for the "malformed" schema and then I realized that we don't check the yamls if the idTemplateCanBeUsedToMatchResourceName is unset:

k8s-config-connector/pkg/resourceskeleton/resourceskeleton_test.go

Lines 74 to 75 in 2f4f2c6

	if !*rc.IDTemplateCanBeUsedToMatchResourceName {
	continue