Fix razzle.cmd: correct MSBuild PATH, VS version range, and exit codes

[DinahK-2SO]

Summary of the Pull Request

• Real exit codes: errors now exit /b 1, success exit /b 0. Old goto :EXIT fell off the end returning success even on error.
• Correct PATH: append MSBuild's bin dir with a ;. Old terminal had no separator (glued onto the last entry) and used fragile terminal.
• Pin VS [17.0,19.0): -latest -prerelease picked any newest VS; for old versions like VS2019 doesn't support building *.slnx (OpenConsole.slnx)
• Guard MSBuild exists: fail fast with fix-it guidance instead of a later cryptic '""' is not recognized.
• Quote "%VSWHERE%": launch vswhere via a quoted path. Unquoted, a repo cloned under a path with spaces (e.g. C:\Users\First terminal.) fails to run vswhere, leaving MSBUILD unset so razzle errors out.
• Consistent casing: MsBuild -> MSBuild in status/error text (cosmetic).

References and Relevant Issues

Nah

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

Run local build

PR Checklist

• Closes #xxx
• Tests added/passed
• Documentation updated
  • If checked, please file a pull request on our docs repo and link it here: #xxx
• Schema updated (if necessary)

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[lhecker]

Thanks!

[DHowett]

/azp run

[azure-pipelines]

Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.