[release/9.0.1xx] Use new ACR for registry image

[github-actions]

Backport of #49677 to release/9.0.1xx

/cc @nagilson @baronfel

[baronfel]

Here's the error being reported:

Unable to find image 'dotnetdhmirror-f8bzbjakh8cga6ab.azurecr.io/registry:2' locally
2: Pulling from registry
44cf07d57ee4: Pulling fs layer
bbbdd6c6894b: Pulling fs layer
8e82f80af0de: Pulling fs layer
3493bf46cdec: Pulling fs layer
6d464ea18732: Pulling fs layer
docker: open /datadisks/disk1/docker/tmp/GetImageBlob3780687031: no such file or directory.
See 'docker run --help'.

The docker daemon is able to access the new registry, but seems to be having problems accessing the file system/disk on the build agent.

[nagilson]

Internal Thread: We need to update the docker version on the machines and that is considered high prio by the engineering system team but they say it make take some time. I dont want to make you very sad but also this is still causing all of the SDK codeflow to be blocked, so we may need to redo #49686

This is a technical workaround and it is bad to disable the tests for this key scenario. But to unblock everything else, I dont see another way around this without spearheading / doing the work of the engineering system ourselves.