Consider Publishing Generator Dev Versions When Running RegenPreview

As part of our developer loop, we run a regen preview pipeline that invokes https://github.com/microsoft/typespec/blob/main/packages/http-client-csharp/eng/scripts/Submit-AzureSdkForNetPr.ps1. This regenerates both unbranded data plane and azure branded data plane libraries from https://github.com/Azure/azure-sdk-for-net. The resulting PR ([example](https://github.com/Azure/azure-sdk-for-net/pull/61050/checks) contains the diffs from the regeneration _but_ the CI in the pipeline always fails because the package.json files were updated to use local artifacts versions created on the host machine.

We should consider publishing these artifacts to the registry configured in the `.npmrc`, then referencing that published version in each relevant package.json file. That way, CI can run in the resulting pr