Filepath for download in output incorrect on Remote machines

**Describe the bug**

When using the Remote SSH extension for VSCode in tandem with AWS Toolkit the file path outputted in the Output console when downloading a file from S3 does not match the actual path of the downloaded file. The file path outputted points to a file on the local machine when it instead should point to the file on the remote machine.

**To Reproduce**

Steps to reproduce the behavior:
1. SSH onto a remote machine using the Remote SSH extension
2. Download a file from S3
3. Command click on the file path written in the AWS Toolkit Output window
4. File cannot be found

**Expected behavior**

The file path written in the output console should point to the file saved in the remote machine, not a file that does not exist on the local machine.

**Screenshots**
*Copied from Console*
Downloading 0029a9b9-6dd1-49eb-81f9-3b15174681b2...
Successfully downloaded file file:///tmp/0029a9b9-6dd1-49eb-81f9-3b15174681b2

**Desktop (please complete the following information):**

- OS: Linux x64 5.4.134-73.228.amzn2int.x86_64
- Visual Studio Code Extension Host Version: 1.60.0
- AWS Toolkit Version: 1.29.0

Reproduce the issue with VS Code Remote SSH and an S3 download, then trace how the AWS Toolkit writes the download path to its Output window. Verify the reported path is resolved on the remote machine and that command-clicking it finds the downloaded file there.

Written by the indexing model from the issue text.