TDML generation produces incorrect relative paths on Windows when run from different drive

## Description

temp TDML File generation from Launch config (when you run a debug session) generated wrong relative file paths when your schema and data files are located in different drive in windows (For example, if you have Cand D drive partitions on your windows machine and if your schema and data files are located on D drive)

This is a edge case found when schema and data files are located on "D" drive on windows but the temp TDML file is generated in "C" drive temp directory.

## Steps to Reproduce

Prerequisite: You have two drives on your windows machine (or your schema files and data files are located on external drive)

- Run a debug session with schema and data file located on external drive or any other drive than windows installation drive (i.e. C drive)

- Try to create TDML file after initial debug session. (This step will copy TDML file from temp directory to user specified directory). This step automatically resolves paths to relative path for schema, data and infoset files.

- Open the TDML file from user specified directory and observe the resolved relative path.

## Expected Behavior

Relative paths should be resolved to relative path in external directory.

## Actual Behavior

It resolves relative paths incorrectly as shown below

## Additional Notes and Screenshots (optional)

## Environment

- Operating System(s): Windows
- Prerequisite: Two drives on your windows machine (i.e. C and D drives) and schema and data files are located on different drive than windows install drive.

Start with the launch-configuration debug-session flow that creates a temporary TDML file, then trace the step that copies it to the user-specified directory and resolves schema, data, and infoset paths. Reproduce the case on Windows with source files on one drive and the temporary directory on another; done means the generated TDML contains valid relative paths.

Written by the indexing model from the issue text.