Set the blob name in sas uri

[Antonstockmarr]

When the sas uri is created for the container the blob name is not specified. By setting the blob name, the sas uri can still be used to copy the blob.

#patch
resolves #116

[Antonstockmarr]

Tested by creating a SAS url from the Azure portal for the container and importing it in the devTools.

[AndreasHassing]

Why do we assume the SAS URL is created for the container, and not the blob? I would assume that we should just create a SAS URL directly for the blob?

[Antonstockmarr]

There is a Geneva Action creating a SAS token for an environment, and the generated token points at the container and not the blob. But if you enter a sas for the blob it would still work.

[AndreasHassing]

There is a Geneva Action creating a SAS token for an environment, and the generated token points at the container and not the blob. But if you enter a sas for the blob it would still work.

Ah, so that's how customers/devs will get the workload instances for now, we pass a read-only SAS URL for the container in the hub's storage account wherein the current.json lives?