All dependencies must come from PyPI before a release can be published on PyPI

[eb8680]

See e.g. this failure: https://github.com/BasisResearch/dynestyx/actions/runs/23252547976/job/67598272779

Claude says:

PyPI explicitly rejects any package whose metadata contains @ dynestyx. in Requires-Dist. The four git dependencies in pyproject.toml (effectful, cuthbert, cuthbertlib, cd-dynamax) need to be published to PyPI first and referenced with normal version specifiers before your package can be uploaded.

[DanWaxman]

There are currently three dependencies we're pulling from git for:

• effectful -- there might have been a reason we started this way in October, but I don't think there is now. Fixed by Use PyPI-based effectful #161.
• cuthbert -- Upgrade cuthbert to current main #159 addresses moving from my custom patch to the current main. There are some critical bug fixes that haven't made it into a PyPI version, so we cannot yet migrate to PyPI entirely, but it should be easy after they cut a new version. [Update]: addressed fully in Upgrade cuthbert to PyPI version #182.
• cd_dynamax -- this will take a bit more work. @mattlevine22 built the current cd_dynamax integrations on a dev branch that likely will not be uploaded to PyPI. We'll have to migrate to the current public API. [Update]: As of Ml plumb to public cd dynamax 2 #169, we now use the public branch -- cd_dynamax just needs a PyPI upload.