[SM-1444] Fix Windows GNU Builds

[coltonhurst]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/SM-1444

📔 Objective

Windows GNU builds are currently broken due to a bug in rustls-platform-verifier when LTO is turned on.

I have submitted a GH Issue for this here: rustls/rustls-platform-verifier#141

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation
  team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
  issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – 7a698926-8f7d-47a0-8315-6da8cb0a4cf6

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Unpinned Actions Full Length Commit SHA	/build-cli.yml: 341	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Fixed Issues

Severity	Issue	Source File / Package
	Unpinned Actions Full Length Commit SHA	/build-cli.yml: 338
	Unpinned Actions Full Length Commit SHA	/build-cli-docker.yml: 131
	Unpinned Actions Full Length Commit SHA	/build-cli.yml: 86
	Unpinned Actions Full Length Commit SHA	/build-cli.yml: 173
	Unpinned Actions Full Length Commit SHA	/release-cli.yml: 192
	Unpinned Actions Full Length Commit SHA	/release-cli.yml: 66
	Unpinned Actions Full Length Commit SHA	/release-cli.yml: 198
	Unpinned Actions Full Length Commit SHA	/release-cli.yml: 58
	Unpinned Actions Full Length Commit SHA	/build-cli-docker.yml: 54
	Unpinned Actions Full Length Commit SHA	/build-cli-docker.yml: 61
	Unpinned Actions Full Length Commit SHA	/release-cli.yml: 124

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.16%. Comparing base (1309527) to head (1c5e1f4).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1053      +/-   ##
==========================================
- Coverage   58.24%   58.16%   -0.09%     
==========================================
  Files         197      197              
  Lines       13504    13523      +19     
==========================================
  Hits         7865     7865              
- Misses       5639     5658      +19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[michalchecinski]

I've added two renaming suggestions to reflect better which systems they should run for. This will result in better visibility of whether the appropriate build step has been run.

[coltonhurst]

@michalchecinski I think it might be beneficial to leave the explicit targets as is?

For musl, it could be two different targets, x86_64-unknown-linux-musl or aarch64-unknown-linux-musl. If we just make it Build rust for musl it won't be immediately obvious which architecture it is.