Patch v0.23 for compatibility with latest NumPy

[dmitrisvetlov]

For reasons that are not entirely clear, the latest version of pycro-manager (v0.34.8 or thereabouts) does not work with our terminator code, and I have heard from colleagues that there may be a bug (identical or different) in that code that is more general. As a result, for the near term it is worthwhile to stick with pycro-manager v0.23, and the corresponding (somewhat old) version of Micro-Manager.

However, this causes a problem for our conda environment, because this old version of pycro-manager is incompatible with the latest version of numpy, which understandably causes artificial version incompatibilities with other packages, some of which can be difficult and time-consuming to diagnose and resolve. (The incompatibility is due to the fact that the old np.bool type was deprecated before 1.24.0 of numpy in favor of the built-in bool (to which it was just an alias). It will return, however, in 2.0.0, as numpy.bool, as indicated in the release notes; see also relevant pull request.)

As a result, we will do the following:

1. Revert this fork of pycro-manager to v0.23, i.e. this commit.
2. Create a patch, v0.23.1, to remove the incompatibility with the latest version of numpy. NOTE: Although v2.0.0 has been released (on June 17, 2024), the latest version in conda remains at v1.26.4.
3. We will reintegrate this into main and only update this fork for one of two reasons: to make subsequent fixes necessary as numpy is updated further, or to upgrade to newer versions of pycro-manager once the underlying bug(s) have been fixed upstream.
4. In our terminator repository, we will update the environment to install this version of pycro-manager rather than the one available via pip. NOTE: To ensure optimum compatibility with the Java bridge, this requires utilizing a specific Micro-Manager version; namely, the December 18, 2022 nightly build.