Ensure that livetests don't clash on uploading test log artifacts (#26481)
Ensure that livetests don't clash on uploading test log artifacts (#26481)

@mccoyp some fallout from the logging improvement.

@LibbaLawrence reached out yesterday about a [failing livetest pipeline](https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1876097&view=logs&jobId=a5c73adf-21c4-51b0-3477-575974909b75&j=53173ce0-af52-5d9c-4521-116e992c2b8d&t=63b43222-0384-512a-fa2b-9cd86c4521e4) for some advice on how to repro it.

While I was there, I noticed that the log upload stage of one of the jobs was failing. This was strange, as there wasn't a case where this should be _possible_.

After digging around a little, I realized that the job names are identical across the stages. 

![image](https://user-images.githubusercontent.com/45376673/192609331-fc8a7366-c791-47f4-97c9-85b7287a09bb.png)

This  means that the first one to pass will upload the log artifact, and then the others will _fail_ when trying to upload it.

By including the stagename in the artifact, we will avoid this unfortunate scenario.
Azure/azure-sdk-for-python,Azure/azure-sdk-for-python,Azure/azure-sdk-for-python,Azure/azure-sdk-for-python