Add notice that the restart is about pwsh not sys

[Legend-Master]

Description

• What does this PR change? Give us a brief description.
• Closes #

I got confused for a second if that's asking me to restart my computer 😂

Also changed the folder selection to select the latest one in case there're multiple version of NDK installed

[netlify]

✅ Deploy Preview for tauri-v2 ready!

Name	Link
🔨 Latest commit	2af88ce
🔍 Latest deploy log	https://app.netlify.com/projects/tauri-v2/deploys/6843c0ed4c13010008bec774
😎 Deploy Preview	https://deploy-preview-3335--tauri-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (🟢 up 1 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[FabianLars]

This is more in line of the old style but without the incorrect assumption

Suggested change

	PowerShell will not pick up the new environment variables until reboot or logout (the PowerShell, not your system),
	however you can refresh the current session:
	PowerShell will not pick up the new environment variables until it is restarted,
	however you can refresh the current session:

the however sounds a bit wrong there, so maybe something like:

PowerShell will not pick up the new environment variables until it is restarted,
or until you manually refresh the session:

or:

To make PowerShell pick up the new environment variables you can either restart it
or run this command:

i'm not too happy with any of them tbh but the PR's suggestion basically tries to correct an incorrect statement (reboot) visibly without actually fixing it if that makes sense?

[Legend-Master]

Makes sense to me, the first thing popped up in my head was this should be about the powershell not the system, so that's why I edited it like this, I think maybe:

Most apps don't refresh their environment variables automatically, so to let them pickup the changes, you can either restart your terminal and IDE or for your current PowerShell session, you can refresh it with

[System.Environment]::GetEnvironmentVariables("User").GetEnumerator() | % { Set-Item -Path "Env:\$($_.key)" -Value $_.value }

[FabianLars]

It's a bit long but works for me until we get an english professor to proof read our docs 😂