chore(deps): bump ilammy/msvc-dev-cmd from 1 to 1.8.0

[dependabot]

Bumps ilammy/msvc-dev-cmd from 1 to 1.8.0.

Release notes

Sourced from ilammy/msvc-dev-cmd's releases.

msvc-dev-cmd v1.8.0

• Replaced a static list of environment variables with dynamic configuration, exporting everything that Developer Command Prompt actually configures (#32)
• Fixed an issue with repeated invocation of this action for reconfiguration (resolved ilammy/msvc-dev-cmd#8)

msvc-dev-cmd v1.7.0

• New exported environment variables, necessary for Swift toolchain to work (#30)
  • UCRTVersion
  • UniversalCRTSdkDir

Thanks to @​triplef for adding those!

msvc-dev-cmd v1.6.0

• You can now specify architectures with aliases (resolved #26).

  - uses: ilammy/msvc-dev-cmd@v1
    with:
      arch: Win32   # same as x86

  Win64 is also supported as an alias for x64 or amd64.

• If some parameter is incorrect, this should cause the action to fail as expected (resolved #27).

Great, another “Marketplace Developer Agreement. Of course I never read it, I'm not a laywer.

msvc-dev-cmd v1.5.0

• Check default vswhere location when it's not available in PATH (#19, #20)
• Add VCINSTALLDIR to list of exported variables, fixing windeployqt (#23)
• Cleaned up unnecessary async calls and improved logging (#21)

Thanks @​NicoG60, @​scamille, @​aminya for making this release happen! 💪

Also, thank you Microsoft for making a modal button to accept your new terms and agreements for publishing actions, which completely destroys input in this text box where you write release description, so I had to type it all again...

msvc-dev-cmd v1.4.1

• Fixed issue with slow execution of the action (#12: #14)
• Updated @actions/core to fix minor security issue (#13)

msvc-dev-cmd v1.4.0

• Improved location of VS batch files using vswhere (#11)
• Miscellaneous minor dependency updates

Thanks to @​aminya for making this release happen!

Known issues:

• This release causes massive increase in build times, so it's not recommended (#12) Use v1.4.1 instead.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually