Fix MinGW builds in CI

[dgburr]

Description

The MinGW stages in CI changed from MinGW-W64 v12.2.0 to v15.2.0 some time within the past 5 weeks. This broke compilation of the check submodule due to the issue described in libcheck/check#364. I have created a PR to try and get a fix merged in upstream. However, even if the fix is accepted upstream, it is not clear to me how we want to proceed for libsbp, since the commit message in #1513 makes it sound as though a very specific version of check needs to be used (specifically https://github.com/swift-nav/check/tree/11970a7e112dfe243a2e68773f014687df2900e8) due to bazel compatibility reasons.

I can think of a few possibilities:

1. Wait for the fix to get merged upstream, then bump libsbp the latest upstream version of check. But maybe this will cause some kind of incompatibility with bazel.
2. Commit this PR as-is (i.e. change the check submodule pointer to point to the fix-mingw branch in https://github.com/swift-nav/check). But again, this might cause some kind of incompatibility with bazel.
3. Create a fork in the https://github.com/swift-nav/check repo based upon https://github.com/swift-nav/check/tree/11970a7e112dfe243a2e68773f014687df2900e8 and cherry-pick the fix from Fix compilation using MinGW-W64 13 and later libcheck/check#364 into it

API compatibility

Does this change introduce a API compatibility risk?

Possible issue with bazel, see above.

API compatibility plan

If the above is "Yes", please detail the compatibility (or migration) plan:

Wait for feedback from @martin4861

JIRA Reference

https://swift-nav.atlassian.net/browse/BOARD-XXXX

[woodfell]

Didn't know we still had check here, I thought everything got moved to gtest

[martin4861]

I think, I am fine with this change (even though the Bazel build and the CMake build will now use different versions of check).
Once libcheck/check#364 is merged, then I can follow up on this topic and I could try to create a new version of check.

Still, the preferred solution would be to use gtest if possible.

[sonarqubecloud]

Quality Gate passed for 'libsbp-c'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dgburr]

No longer needed due to #1527