fix: handle properly np.cross() - 2d ops deprecated in Numpy 2.X

[RobPasMue]

Description

As title says - once Numpy 1.X is not used anymore we can remove this.

Issue linked

None

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate unit tests.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have added the minimum version decorator to any new backend method implemented.
• I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

[AlejandroFernandezLuces]

LGTM, it's wild that we need to do the cross operation that way. I see that they are going to implement a proper operation soon, can we add a TODO or some reminder to change this when np.linalg.cross2d is implemented?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.85%. Comparing base (e8017a6) to head (1023459).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1419   +/-   ##
=======================================
  Coverage   91.85%   91.85%           
=======================================
  Files          86       86           
  Lines        6875     6878    +3     
=======================================
+ Hits         6315     6318    +3     
  Misses        560      560           

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

[RobPasMue]

LGTM, it's wild that we need to do the cross operation that way. I see that they are going to implement a proper operation soon, can we add a TODO or some reminder to change this when np.linalg.cross2d is implemented?

Sure - though I am not sure they will even implement it... they have preferred documenting it over implementing numpy/numpy#26692 and numpy/numpy#26620 (comment)

More importantly... see this numpy/numpy#26640 and especially numpy/numpy#26640 (comment) and numpy/numpy#26640 (comment)

I don't think it'll ever be implemented honestly...

[AlejandroFernandezLuces]

LGTM, it's wild that we need to do the cross operation that way. I see that they are going to implement a proper operation soon, can we add a TODO or some reminder to change this when np.linalg.cross2d is implemented?

Sure - though I am not sure they will even implement it... they have preferred documenting it over implementing numpy/numpy#26692 and numpy/numpy#26620 (comment)

More importantly... see this numpy/numpy#26640 and especially numpy/numpy#26640 (comment) and numpy/numpy#26640 (comment)

I don't think it'll ever be implemented honestly...

Forget about the reminder then 😄

[RobPasMue]

Forget about the reminder then 😄

Haha! 😄 good then - thanks for pointing it out though! It would've been the way to proceed (if they had decided to eventually implement it... but I think it's not the case - I'll keep an eye on NumPy though and the issues)

[RobPasMue]

@AlejandroFernandezLuces - I just pushed @MaxJPRey's suggestion to typehint it as well. Can you approve?

[MaxJPRey]

@AlejandroFernandezLuces - I just pushed @MaxJPRey's suggestion to typehint it as well. Can you approve?

Done @RobPasMue