Ensure all paths have been fully expanded before operating on them

[HowardWolosky]

Shortened paths (like c:\program~1 for c:\program files) don't get expanded by Resolve-Path. This normally wouldn't be a problem except for instances of logic where we retrieve a list of files under that path, and then attempt to parse out that root path (example: in PackageTool, when we do this:

$split = $xmlFilePath -split $PDPRootPath, 0, "SimpleMatch | Where-Object { -not [String]::IsNullOrWhiteSpace($_) } | Select-Object -First 1
$language = $split -split "\", 0, "SimpleMatch" | Where-Object { -not [String]::IsNullOrWhiteSpace($_) } | Select-Object -First 1

In a scenario like that, the full name of the file will be expanded and not the shortened version, thus the initial part won't be correctly lobbed off.

We need to do something like this:

$inputPath = (Get-Item -Path $inputPath).FullName

for any $inputPath that we get from the user where a scenario like this might be possible. That will ensure that the path is expanded before we operate on it.