expand passed-in path in order to workaround a dotnet cli bug

[baronfel]

Fixes #2013 by expanding the giventool-path using just shell builtins. If you have the fake tool installed already you'll need to clear that directory before using this fix.

@samritchie want to give this a try?

[matthid]

@baronfel can you please test this on staging before we release it? Also what does "you'll need to clear that directory" mean? You will update the template and it will work, correct?

[matthid]

Thanks!

[baronfel]

if you've got a fake binary at the tool path already it'll have the badly-formed path embedded in it, so there's no way to overwrite that aside from reinstalling the tool. the easiest way to do that is to remove the toolpath folder and rerun the fake.sh script.

When you say 'test in staging' what does that mean? is there a prerelease version that will be deployed that I could install?

[baronfel]

(I will note that this fix applied to our work tool scripts unblocked us enough to move full ahead on fake 5's netcore runner :D )

[samritchie]

Yep, this script works, thanks. It makes building in a container simpler, as none of the available SDK images seem to have the global tools dir on the path.