save winget curl to user/system PATH

Relevant area(s)

WinGet CLI

Description of the new feature / enhancement

Right now, when you upgrade curl for windows through winget (id is cURL.cURL), you have to every time replace the PATH variable on the environment variables to contain the new directory name. For example, if you upgraded from curl 8.18 to 8.19, so the directory where curl.exe will be saved, will be named slightly different due to the version change. So my idea is to automate this during the installation of curl, but this can apply also to other packages as well that the user would like to be saved to his PATH variable (like openssl, ruby, php etc.), instead of doing it manually.

Proposed technical implementation details

An example to a powershell script snippet I wrote that for now do this job for me every time I upgrade curl:

$Old_CURL_Path = ($env:PATH -split ';' | Select-String -Pattern "cURL.cURL").ToString()
$New_CURL_Path = (Get-ChildItem -Path "C:\Users\myusername\AppData" -Filter "curl.exe" -Recurse).DirectoryName
[System.Environment]::SetEnvironmentVariable("PATH", ($env:PATH).Replace($Old_CURL_Path,$New_CURL_Path), [System.EnvironmentVariableTarget]::Machine)
}

The issue identifies the WinGet CLI as the relevant area but names no source files, tests, or entry points. Start by tracing how package installation and upgrades handle installed paths and environment variables, then determine how a package could opt into PATH management safely. Done means upgrades can keep the selected package executable available on the user or system PATH without manual version-path replacement, with coverage for curl and the broader package case.