Switch the Android stdlib build and compiler validation suite config to versioned target triples

[finagolfin]

Description

Now that availability version checking for Android was merged, #84574, and appears to be working well, we should switch the stdlib build and validation suite over to using versioned target triples, as they are the only remaining portions of Swift that don't use such versioning yet and a few tests will start breaking without it.

@compnerd and @etcwilde, would this be a good candidate for the new Runtimes/ CMake config?

We can hold off on this until we switch the Android CI to NDK 28 or later, which the static version-checking @madsodgaard added requires.

Additional information

I am not sure how much work this is or if anybody has tried it yet. I don't think we want to start versioning the module triples too, just building with a specific minimum target version as done for the rest of the corelibs already, and perhaps surfacing that info somewhere in the final product.

[compnerd]

I don't see any reason that this wouldn't fit into the new runtimes build. It should be relatively straightforward once the supporting changes for the tests are done.