{P} Column-physics gt4py.cartesian features & debug

[FlorianDeconinck]

Looking at Physics code with can see patterns for:
- global table
- k-indirect writes
- for-loops
- common
- subset of K
- code-flow interrupt
- data dimensions parallelism

Most if not all of those should be represented as first citizens with gt4py.cartesian to allow for easy implementation.

---

• GT4Py.cartesian: global fields NDSL#1
• GT4Py.cartesian: K indirect write NDSL#2
• GT4Py.cartesian: code-flow interrupt NDSL#10
• GT4py.cartesian: For loop NDSL#11
• GT4Py.cartesian: data dimension parallelism NDSL#22
• [Bug] GT4Py.cartesian: dace:X backends while is read-only NDSL#40
• [Bug] Data dimensions: silent unroll NDSL#43
• [Bug] Data dimensions: wrong rhs has no feedback NDSL#44
• True mixed precision NDSL#55
• Mixed precision: type hint and cast for GT4Py NDSL#58
• Implement a replacement for Fortran PRESENT(X) #85
• Add pure python debug backend NDSL#59
• Python is construct is forbidden and should error out at gtscript level NDSL#60
• [Bug] While loop and function create bad generation (dace:cpu) NDSL#62
• Hybrid indexing (absolute index in K) NDSL#64
• K dynamic indexing mitigation: check for out of bounds NDSL#65
• Approximation table calculation #90
• [GT4Py] Turn on new debug unit test for ALL_BACKENDS #98