windows-gnu: enable native TLS

[mati865]

Since Rust 1.98 we have declared minimal supported versions for the tools like the linker. That means native TLS is supposed to work now as seen in try builds in: #156819
Therefore, this change is very likely to cause issues if somebody still doesn't adhere to the requirements. As such I don't know what form of approval will be required.

Fixes #91659
Fixes #135719

[mati865]

@bors try jobs=x86_64-mingw,i686-mingw

[rust-bors]

☀️ Try build successful (CI)
Build commit: ae7651c (ae7651caf0169462998355116a349c00c6f4d9c1)
Base parent: 561ea2b (561ea2bfa3022226082e2db39d6ccb241e9e34bc)

[mati865]

Labelling libs because changes like #156743 will no longer be testable on windows-gnu toolchains as they will now utilise the same code path as other Windows targets (gnullvm and msvc).

Upd: T-libs seems to be onboard with this change: https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/Enabling.20native.20TLS.20for.20windows-gnu/with/622302693

[rustbot]

r? @TaKO8Ki

rustbot has assigned @TaKO8Ki.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: compiler
• compiler expanded to 75 candidates
• Random selection from 18 candidates

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.