Summary of the new feature/enhancement

This was brought up in the PR #11552 to expand ~ for PATH making it consistent with BASH and resolving an issue with dotnet global tools which adds a path starting with ~ to PATH. ~ expansion is done by the shell and not the OS, so this can lead to unexpected behavior if this isn't understood. From that perspective, it seems that using ~ as shortcut to refer to $HOME is ok for interactive use, but probably not recommended for system config changes as other shells may not support it.

From that perspective, it may not make sense to use it for LD_LIBRARY_PATH nor PSModulePath, but I can also see an argument that developers may want to use this during development rather than an absolute path. Thoughts?