Add-Debug-Profile needs to handle new emitter changes

Add-Debug-Profile uses tsp-client to bootstrap the tspCodeModel. This ends up using whatever version of the emitter is specified in the tsp-location.yaml. We should attempt to use the local unbranded emitter so that any local changes are reflected in the tspCodeModel. We should probably use the same approach as the RegenPreview script and possibly just use the code defined there to instead build a local unbranded emitter, then update the azure-sdk-for-net artifacts to reference that local build. Then build a local Azure emitter and update the artifacts to reference that. I think the majority of Add-Debug-Profile impl can be deleted and we can reuse RegenPreview to accomplish the same thing. The end result should be that we have a local tspCodeModel/modified launchSettings that can be used for debugging. The changed artifacts can be `git restored` after the script completes.