MAINT: skip failing cython limited API tests on Cython 3.3.0 - #32407

Thanks Nathan.

@charris please don't backport this just yet, I think there is a decent chance that the test is wrong. See #32393 (comment).

@rgommers OK

This test could still really benefit from a clear explanation of what it's actually doing. The extension module is built only once, so what is and isn't covered by calling _check_api_module multiple times with different versions of python and numpy for the name of mod?

This came in from #31822 by @kumaraditya303 and reviewed by @ngoldbaum. The PR does not have an issue attached, the only hint to the reason for it being added was

I've expanded tests to cover the datetime APIs which was broken recently to avoid such future breakages.

I did not see any review around the module being built only once. I think the intention was to build it for each iteration of the test. But I may be wrong.

@mattip Building once is intentional, the single meson build compiles a separate module for each (abi3 python, numpy target) combination, see the loops in examples/limited_api/meson.build. Each parametrized test imports its own module by name (e.g. limited_api_cython_3_11_npy2_2) so every iteration tests a differently compiled binary. Rebuilding per test would just produce the same binaries serially. I think this test caught a real Cython bug where any process importing two abi3 cython modules targeting <3.11 and 3.11 was affected.

I'm convinced now, thanks for the explanation added in gh-32444 Kumar.