Tracking issue: Caiman and numpy 2.0

[pgunn]

numpy 2.0 has release candidates, so a full release is just around the corner.

Right now caiman pins numpy at <2.0.

There's no need to try to test/fix our code before the 2.0 release, but it should be on our radar to adjust our code for 2.0 in the mid-term. Depending on the issues that come up we may:
A) Be able to get along with both versions, or
B) Need to treat this as a gate, doing a minimum version pin after the adjustments

I see both as acceptable, although the former is preferable because we'd be less all-elbows with other packages and user environments.

[kushalkolar]

numpy v2 just released a few hours ago and is already causing problems elsewhere 🫠 , need to wait for other packages (such as skimage) to make new released compiled against numpy v2

[FlynnOConnell]

Numpy is giving me issues on rigid + nonrigid motion correction:

 line 3153, in motion_correction_piecewise\n    res = dview.map_async(tile_and_correct_wrapper, pars).get(4294967)\n  File "C:\\Users\\RBO\\AppData\\Local\\Programs\\Python\\Python310\\lib\\multiprocessing\\pool.py", line 774, in get\n    raise self._value\nValueError: Unable to avoid copy while creating an array as requested.\nIf using `np.array(obj, copy=False)` replace it with `np.asarray(obj)` to allow a copy when needed (no behavior change in NumPy 1.x).\nFor more details, see https://numpy.org/devdocs/numpy_2_0_migration_guide.html#adapting-to-changes-in-the-copy-keyword.\n'

On numpy==2.0.2, caiman==1.11.3