Remove a resolve-path from Get-PrPkgProperties

[scbedd]

This PR will enable PR invocations of generate-job-matrix won't crash when the files don't actually exist on disk.

My only concern is the following scenario:

I have some FUD around a scenario where a PkgProps file is generated on windows and then we check -like PkgProps.DirectoryPath against a path checked out on a different OS.

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[weshaggard]

What cases do we have where these files aren't on disk? Even without the resolve wouldn't that cause trouble?

[scbedd]

What cases do we have where these files aren't on disk? Even without the resolve wouldn't that cause trouble?

During generate-job-matrix is where this breaks, because we use Get-PrPackageProperties to get the targeted set of packages + matrix configs.

EDIT: it looks like this when it blows up the way I'm resolving in this PR.

Even without the resolve wouldn't that cause trouble?

If it does, I am not seeing it. We're basically only using that Resolve-Path to ensure that the paths are all coherent for a platform. Not attempting to like a path/like/this with a path\\like\\this for instance.

However, it's unnecessary to add this Resolve-Path, as whatever directory path will be freshly generated on the same machine. This is just a straight up unnecessary piece of code that we're removing.