How to have a consistent Provisioning UDID?

[brzzdev]

Now that #943 is closed, and we can once again register Provisioning UDIDs with Apple we're seeing something rather strange.

Before, each image would have a consistent Provisioning UDID and although we had to add that to the Apple dev portal each time there was a macOS or Xcode update, it was relatively sustainable.

Now we're observing a different Provisioning UDID on each launch, although Serial Number and Hardware UUID remain consistent.

It seems we can only get a constant Provisioning UDID by running the image on the same runner that built it, and by running only one VM at a time.

As you can imagine, this is quite a drawback and would mean registering as many UDID's as runners we have on every macOS or Xcode update, as well as limiting the number of pipelines that can run in parallel.
Apple only allows 100 devices, and limits the changes per year, so this is unsustainable.

Do you have any idea what might have changed for us here?

An option to pass a hardcoded Provisioning UDID to tart would be incredible and mean that we only ever need to use up one of our 100 spots.