cartesian: Daily CI failures with MacOS + py > 3.11 + uv "highest" strategy.

[FlorianDeconinck]

Per #2438

The following error happens in daily CI on macOS, only for the uv highest resolution strategy.
libc++abi: terminating due to uncaught exception of type std::runtime_error: thread_specific_storage constructor: could not initialize the TSS key!
TSS / TLS is the thread-local storage, and apparently the operating system refused to allocate a new thread-specific key. An explanation is that macOS has a low limit on TSS / TLS keys and, unlike Linux, macOS does not scale.
We could not find a way to workaround this issue, so we disable the failing test configuration for now.

Changes to the loop order and residency of the transient memory done in #2426 have triggered those failures, as per this successful CI run

Linux is fine and so is 3.11 or the "lowest" UV strategy on MacOS.

Unproven ideas to dig in are:

• an OOB read/write caught oddly
• something related to OpenMP & thread count (but feat[cartesian]: Allow OpenMP to be deactivated #2435 didn't help)

New MacOS image and different compilers have been tested.

Example of failing CI are here, there or there