Increase minimum Android API level to 24

[mhsmith]

This PR is stacked on top of #125941, which should be merged first. However, this PR should not be backported to 3.13, because that has already committed to a minimum API level of 21.

API level 24 was released in 2016, and according to https://dl.google.com/android/studio/metadata/distributions.json, over 97% of active devices are on that version or newer.

Because of limitations in the pidof and logcat commands, 24 is already the minimum API level supported by the test script – older versions had to be tested manually. So this will save some work for Python 3.14.

[mhsmith]

!buildbot android

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @mhsmith for commit 55cfb94 🤖

The command will test the builders whose names match following regular expression: android

The builders matched are:

• aarch64 Android PR
• AMD64 Android PR

[freakboy3742]

The change itself makes sense; but there's a merge conflict after #125941 landed; once that's resolved, I think this is good to land.

[freakboy3742]

👍

[freakboy3742]

Not sure why this passed a buildbot check on the PR, but then failed on the main... any ideas @mhsmith ?

[mhsmith]

Actually it did not pass the buildbot check on the PR (click the red X against the "Remove skip" commit above).

It looks like increasing the minimum API level has caused some additional libc APIs to become available at compile time, but they always return "permission denied" at runtime. This is a pretty common situation, so I'll make another PR to fix it.

[freakboy3742]

/me facepalms.

I missed the original test failure, then assumed that the impact of a buildbot test failure would carry over into the subsequent merge-with-main build.