New feature to update SAS token during transferring

### Which service(blob, file) does this issue concern?
All

### Which version of the SDK was used?
0.8.1.0

### On which platform were you using? (.Net Framework version or .Net Core version, and OS version)
Both .Net Framework and .Net Core, on all supported OSes.

### How can the problem be reproduced? It'd be better if the code caused the problem can be shared.

### What problem was encountered?

### Have you found a mitigation/solution?

This is a new feature request which should impact all services.
DMLib can be used to transfer large amount of data which would spend long time. SAS token used in transfer could be expired during the process. Customer would want a way to update SAS token for long running transfer.
Quotes:
"One of our scenario is where SAS token expires during or before operation, do you have any recommended way to handle it, I can handle it using our own retrial logic but just wanted to check if DML provide any of this capability."

The issue names no files, tests, or entry points. Start by locating the DMLib transfer paths for blob and file services, then determine how long-running transfers currently use SAS tokens and define the expected behavior for refreshing an expired token across all services.

Written by the indexing model from the issue text.