GeezerVison

Issue: gh-161870
build-details.json records sysconfig.get_platform() from the build machine, and test_platform compared that value with the one computed at test time. On Linux, os.uname() reports the kernel's machine name, so for a 32-bit build the two can differ when the build machine and the test machine see the same architecture under different names: linux-i686 != linux-x86_64 for Debian i386 packages on an x86_64 kernel, linux-armv7l != linux-armv8l for Ubuntu armhf, and so on.

The recorded value describes the build and is not wrong, so this only relaxes the test: when the two platforms differ and the running interpreter is a 32-bit Linux build, the test now skips instead of failing. In every other case the comparison stays strict, including for a mismatch seen by a 64-bit build.

Testing (Linux x86_64, debug build):

./python -m test test_build_details test_sysconfig passes with the unmodified file, so the strict comparison still holds when the values match.
With the recorded platform changed to linux-i686, the old test fails with AssertionError: linux-i686 != linux-x86_64, the same pair reported in the issue. With this change the test skips for a 32-bit interpreter (simulated with sys.maxsize = 2**31 - 1, the same approach test_sysconfig uses) and still fails for a 64-bit one, where a mismatch is not expected.