fix: respect array type in wrong-mode pushforward/pullback

[gdalle]

DI source

• In pushforward/pullback, give x/y as a first argument to the map over cartesian indices. This allows array types (e.g. static or GPU) to be preserved.

[codecov]

Codecov Report

Attention: Patch coverage is 75.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 64.44%. Comparing base (8ef803c) to head (0955815).
Report is 11 commits behind head on main.

Files with missing lines	Patch %	Lines
...rentiationInterface/src/first_order/pushforward.jl	50.00%	3 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (8ef803c) and HEAD (0955815). Click for more details.

HEAD has 30 uploads less than BASE

Flag	BASE (8ef803c)	HEAD (0955815)
DIT	8	6
DI	37	9

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #620       +/-   ##
===========================================
- Coverage   97.95%   64.44%   -33.51%     
===========================================
  Files         119      114        -5     
  Lines        6246     6258       +12     
===========================================
- Hits         6118     4033     -2085     
- Misses        128     2225     +2097     

Flag	Coverage Δ
DI	53.79% <75.00%> (-45.13%)	⬇️
DIT	86.96% <ø> (-8.96%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gdalle]

The issue at the moment is with GPUArrays because CartesianIndices(x) is not a GPU array