Skip pal::realpath() error logging while probing directories
Both paths calling pal::realpath() and check its return value to see if
the probed paths actually exist in the filesystem; they do have logic
to handle those paths not existing, and printing error messages while
doing so isn't helpful for the user.
This happens when an application is published with one user but is
executed with another user -- for instance, when using containers (see
issue dotnet/core-setup#4038 for details).
Fixes dotnet/core-setup#4038.
Commit migrated from https://github.com/dotnet/core-setup/commit/
024d2c0150c1ea356cfb33b2bcec91b39509084c