libc-test: port windows to use ctest-next

[mbyx]

Description

This PR adds support for testing the windows platform using ctest-next as well as the original ctest. A minor bug was also fixed along the way, where we have some public primitive types that aren't available in C (this can be fixed with skips instead as well).

Sources

Checklist

• Relevant tests in libc-test/semver have been updated
• No placeholder or unstable values like *LAST or *MAX are
  included (see #3131)
• Tested locally (cd libc-test && cargo test --target mytarget);
  especially relevant for platforms that may not be checked in CI

[mbyx]

Not sure what the arm-linux-androideabi is about. Also since ctest-next is more specific about renaming and skipping types it is possible I might put say a struct type in a rename union type block accidentally, and I wouldn't be able to figure it out.

[tgross35]

Fyi, once #4594 and #4601 merge, I'm happy to just replace the existing ctest impls rather than keeping both for a little while

[tgross35]

(updating the status)

[tgross35]

I didn't mean to delete all of the original ctest right now :), only that you can swap a target from ctest to ctest-next rather than running both for that specific target

[mbyx]

So I should keep test_windows but only run test_windows_next?

[tgross35]

What's the difference with original ctest here?

[mbyx]

ctest uses a single method for renaming types, whereas we have multiple, so that gets split up.

[tgross35]

In ctest we should rename this function rename_alias or rename_type_alias, I was thinking it handled all types for a bit

[mbyx]

It handles all non struct and union types, we don't actually have a rename_alias method (although we can add it), since ctest doesn't use it. But rename_alias would be a different method (rename_type uses MapInput::Type, rename_alias would use MapInput::Alias).