[storage-file-datalake] Allow DataLakePathClient.move() use sas to authenticate source and destination (Azure#12769)

* Make storage-file-datalake move() support adding both sasToken to x-ms-rename-source and the destination url

* Format

* Add comment to util function

* Fallback to use the source's SAS if both
- source authenticates with SAS
- destination isn't provided a SAS

* Reformat

* Do not encode sas query parameter values in x-ms-rename-source header

* Don't set query parameter for snapshot or versionid at the destination when fallback to use sas token in the source url

* Reformat

* Resolve merge conflict

* Remove fallback logic
Throw an error when the source path contains multiple ? query strings, causing ambiguity

* Encode source path segment by segment to avoid encoding "/" characters

* Add unit tests for move operation with SAS credentials

* Add move related test recordings

* Add a bullet for the fix in the change log

* Take PR suggestion

Co-authored-by: Lin Jian <lijian2@microsoft.com>

Author: JasonYeMSFT

sdk/storage/storage-file-datalake/CHANGELOG.md

@@ -2,6 +2,7 @@
 
 ## 12.3.0-beta.2 (Unreleased)
 
+- Bug fix - `DataLakePathClient.move()` now supports source and destination authenticated with SAS. Fixed bug [12758](https://github.com/Azure/azure-sdk-for-js/issues/12758).
 - Now you can get the functionality of the root directory via the `DataLakeDirectoryClient` created via `FileSystemClient.getDirectoryClient("")`. Fixed bug [12813](https://github.com/Azure/azure-sdk-for-js/issues/12813).
 
 ## 12.3.0-beta.1 (2020-12-09)