Use vswhere.exe in Windows pipeline

[KyrietS]

What does this PR do?

Use vswhere.exe to get a path to the vcvarsall.bat.
My approach is that I use PowerShell to execute vswhere.exe and save its result to variable ($vcvarsall_path).
Then, run the script in legacy cmd.exe.

Resolves #1819

Did you check all the boxes?

• Focus on a single fix or feature; remove any unrelated formatting or code changes
• Add unit tests showing fix or feature works; all tests pass
• Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
• Follow our coding conventions
• Minimize the number of commits
• Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

[nickclark2016]

Sorry it took so long for me to review. Can you rebase to latest master and I'll pull it in?

[KyrietS]

Rebased on top of master.
Please, don't feel pressured to work fast. We are here because of passion, not duty. Thanks! 😊

[nickclark2016]

I'm blanking. What merge strategy do we use again? I'm happy with changes

[KyrietS]

Do we have a strategy? 😅
I always click the "Merge pull request" button. I know that it creates a redundant merge commit but it has never been a problem. Starkos has always done it this way, so I do doing the same 😁

EDIT:
But if you're asking about who should click the "Merge" button on GitHub then I'm not aware of any rules. Maybe we should have some 😄. I personally try not to merge my own commits but when it's kind-of urgent then I wouldn't hesitate.

[nickclark2016]

Do we have a strategy? 😅 I always click the "Merge pull request" button. I know that it creates a redundant merge commit but it has never been a problem. Starkos has always done it this way, so I do doing the same 😁

EDIT: But if you're asking about who should click the "Merge" button on GitHub then I'm not aware of any rules. Maybe we should have some 😄. I personally try not to merge my own commits but when it's kind-of urgent then I wouldn't hesitate.

Ahh, talking about merge strategy. Create a Merge Request, Squash and Merge, Rebase and Merge

[KyrietS]

Ahh, talking about merge strategy. Create a Merge Request, Squash and Merge, Rebase and Merge

See Premake's commit history. In most cases, we use Create a merge commit. As far as I know, no strategy has been agreed upon