Create test version of Kusto tables for unofficial pipelines

[lbussell]

This is a follow-up to https://github.com/dotnet/dotnet-docker-internal/issues/8105.

With the introduction of official/unofficial pipelines split, we'd like to exercise the ingestKustoImageInfo step during unofficial publishing if possible.

docker-tools/eng/common/templates/jobs/publish.yml

Lines 186 to 206 in 7841dec

	- template: /eng/common/templates/steps/run-imagebuilder.yml@self
	parameters:
	displayName: Ingest Kusto Image Info
	serviceConnections:
	- name: kusto
	id: $(kusto.serviceConnection.id)
	tenantId: $(kusto.serviceConnection.tenantId)
	clientId: $(kusto.serviceConnection.clientId)
	internalProjectName: ${{ parameters.internalProjectName }}
	condition: and(succeeded(), eq(variables['ingestKustoImageInfo'], 'true'))
	args: >-
	ingestKustoImageInfo
	'$(imageInfoContainerDir)/image-info.json'
	'$(kusto.cluster)'
	'$(kusto.database)'
	'$(kusto.imageTable)'
	'$(kusto.layerTable)'
	--os-type '*'
	--architecture '*'
	$(dryRunArg)
	$(imageBuilder.commonCmdArgs)

We should have a test Kusto cluster which we can ingest build telemetry to. This will help prevent us from making unexpected breaking changes to the publish stage in our pipelines.

One other idea I had - can we use the Kusto Emulator container image during unofficial builds, or even PR validation/eng validation? https://learn.microsoft.com/en-us/azure/data-explorer/kusto-emulator-overview

Maybe we can even reference it as a container resource so it's available during the pipeline run.