Enable automation for test-proxy push

Currently, the test-proxy is installed automatically, with version pinned to this version.

With a simple process start against the downloaded dll.

@JoshLove-msft I believe the actual file is downloaded and unzipped by the msbuild configuration. For python and js, the downloaded exe is just placed in a local directory at the root of the repo for easy re-use. What do you think about that? Or would your recommendation be:

Just install it for yourself

To be fair for .NET, unlike JS/Python, IS THE LANGUAGE that test-proxy was written in. That makes it a bit less out of your way to install it versus what it would be for the others.

Opening this issue to drive discussion. CC @kinelski as he brought this up in test-proxy scrum.

[JoshLove-msft]

The prompt would only occur if there are local staged changes in the assets repo so I don’t think it would impact any automated pushes. In terms of the experience in VS, I think we would need to test it out to see what happens.

[JoshLove-msft]

Perhaps we could add a prompt as a post recording test run that could ask if they want to push the recordings or not.

Fair enough - I think this is a good idea.

We should also probably auto-install the test proxy tool locally during test run (if not installed already) in case users want to interact with the test proxy directly and use any of the other supported commands. See https://github.com/Azure/azure-sdk-tools/tree/main/tools/test-proxy/Azure.Sdk.Tools.TestProxy#via-local-compile-or-net