User hardlinks for various shims/aliases

[eugenesvk]

Is your feature request related to a problem? Please describe.
Currently all different aliases of the same executable "shim" that reads path from the ...__target__ file are duplicate files.

Describe the solution you'd like
Instead of having separate duplicate files for each identical shim, they should all be hardlinks with only a single separate shim (well, 2: python and pythonw) similar to how, for example, git does it.

Describe alternatives you've considered
n/a

Additional context
n/a

[zooba]

Yep, would be open to this. The single shim executable is part of the install, and I expect in most cases it'll be possible to hard link to it rather than copying (though we need to keep the fallback in case it can't be linked).