Update available environment variables so the user does not need to restart their terminal

Description of the new feature / enhancement

Some software that is installed adds itself to the PATH environment variable. These changes are not surfaced to the current terminal session and requires the user to close the terminal and open it again. I consider this to be a huge blocker for creating fully automated software installations as the environment variables it added are often needed in the next step.

Consider NVM as per the docs here: https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows

winget install --id=CoreyButler.NVMforWindows  -e

Followed by another line in the same script (again, as per the docs):

nvm install latest

Results in:

PS C:\Users\User\AppData\Roaming\nvm> nvm install latest
nvm : The term 'nvm' is not recognized as the name of a cmdlet, function, script file, or operable program.

Proposed technical implementation details

WinGet or Terminal should update the user environment variables in order to unblock automated installations of software

Start by reproducing the documented winget install followed by nvm install latest sequence in the current terminal and inspect how WinGet or Terminal handles environment variables. Done means environment changes from an installation are available to the current terminal session without closing and reopening it, so the subsequent nvm command succeeds.