chore: 📦 Update dependencies

[PasteurBot]

This PR updates the lockfile to the latest versions of the dependencies.
Please review the changes and merge when ready.

[apaleyes]

The reason for this failure is explained in jax 0.7.2 release notes:

JAX now represents constants in its internal jaxpr representation as a
LiteralArray, which is a private JAX type that duck types as a
numpy.ndarray. This type may be exposed to users via custom_jvp rules,
for example, and may break code that uses isinstance(x, np.ndarray).

Would be sufficient for jax.typing.ArrayLike to include this new LiteralArray type, but apparently this was missed. Good news, we are not the first to notice, an issue exists.

I see two possible approaches here:

1. Apply a fix ourselves. It will be version dependent unfortunately, because jax 0.7.2 does not work with python 3.10. So we'll have to do something like if LiteralArray exists, add it and redefine ArrayLike.
2. Do nothing, sit on this open PR until jax fixes the typing discrepancy, and then presumably merge when 0.7.3 comes out.

@xalelax what do you think?

[xalelax]

I would sit on this one and go with 2 if that's fine by you!

[apaleyes]

jax 0.8.0 is out, and the typing issue is fixed there. Unfortunately, a new problem cropped up, jax's array turns up where numpy array should be:

AttributeError: 'TypedNdArray' object has no attribute 'tobytes'