[cartesian]: Mitigation for K offset write

[FlorianDeconinck]

The new write offset in K means we can go out of bounds without the system being able to warn about it since extent calculation won't be able to cover those access.

Think about the degenerate case of

index = some_bad_math_that_gives_back_2349082093840
field[0, 0, index] = value

This was an iron rule for GT4Py that we now allow to be broken so we can match patterns seen regularly in physics.

To mitigate the issue, we should introduce on DEBUG a bound check, drop before every K offset write which should error out cleanly.

---

• On DEBUG generate a check for bounds before K offset write

[romanc]

can't edit but I think the code should be

index = some_bad_math_that_gives_back_2349082093840
field[0, 0, index] = value