docs: enhance Windows prerequisites with MSVC and SDK verification steps

[Rohan170603]

Improves the Windows prerequisites documentation by making the Microsoft C++ Build Tools requirements easier to verify and troubleshoot.

• Adds explicit verification of MSVC v143 and Windows 10/11 SDK in the Visual Studio Installer's Individual components tab
• Adds a verification step using link.exe /? in the Developer Command Prompt for VS 2022
• Adds troubleshooting guidance for cases where link.exe is not recognized
• Adds troubleshooting guidance for missing Windows SDK components

These changes help users verify their Windows build environment before attempting to build a Tauri application, reducing common setup errors and confusion.

[netlify]

✅ Deploy Preview for tauri-v2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	d7f7f1e
🔍 Latest deploy log	https://app.netlify.com/projects/tauri-v2/deploys/6a834942b20d3f00081ff519
😎 Deploy Preview	https://deploy-preview-4063--tauri-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

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

[Legend-Master]

Hmm, did you have trouble after setting up the MSVC following the above instructions? I'm not sure how useful it is to have a verification guide that basically says the same thing as doing a above again

[Rohan170603]

Thanks for pointing that out. The intent was to provide a quick way to verify that link.exe is actually available in the development environment after installation, rather than repeat the installation steps.

I agree that the distinction isn't clear enough in the current version. I'll revise the section to make the verification and troubleshooting purpose clearer and keep it concise.