Lock NumPy to versions below 2.0

[m-decoster]

Describe your changes

Locks numpy < 2.0 for all packages, because our OpenCV version was incompatible with newer NumPy versions.

See, e.g., this workflow run: https://github.com/airo-ugent/airo-mono/actions/runs/13111963494/job/36577677885

Checklist

• Have you modified the changelog?

[tlpss]

@m-decoster, do we want to lock on np < 2? or should we test with a newer version of opencv?

Afaik the reason to lock opencv was bc the API tends to change, but not because of specific issues we had with newer versions. @Victorlouisdg (sorry 😛) do you remember any specific issues?

[m-decoster]

@m-decoster, do we want to lock on np < 2? or should we test with a newer version of opencv?

OpenCV version 4.10.0.84 works with numpy>=2, but I haven't tested other libraries yet (and also need to test if all existing code still works)

[Victorlouisdg]

@tlpss I also believe locking OpenCV was a precautionary measure. I also vaguely recall that the ArUco detection API underwent a breaking change once.

[m-decoster]

After a short discussion with @tlpss, I suggest:

• Locking to numpy < 2 for now
• Create a tracking issue to upgrade to numpy >= 2 when we have time to do extensive testing