[ci] Use stable-i686-pc-windows-msvc target for release SM binary in Windows

[bonigarcia]

Description

This PR reverts the use of stable-i686-pc-windows-gnu for the stable release of SM in Windows, and it uses stable-i686-pc-windows-msvc instead.

Motivation and Context

That target was changed since stable-i686-pc-windows-gnu is required to build the SM binary with debug symbols. But it seems this new binary is detected as malware by some antivirus, as reported in #13130. Therefore, we can use stable-i686-pc-windows-msvc for the release SM in Windows (which seems safer for antivirus) and stable-i686-pc-windows-gnu for debug (only used for particular troubleshooting uses).

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.