Loosen dependency version constraints for pyo3, serde, and serde_json

[LockedThread]

Description:

This PR updates the version constraints for the dependencies in our Cargo.toml file to provide more flexibility in dependency resolution. Specifically:

• Main Dependencies:

  • Changed pyo3 from "0.23.0" to ">=0.23".
  • Changed serde from "1.0.190" to ">=1.0".

• Dev Dependencies:

  • Updated pyo3 from { version = "0.23.0", features = ["auto-initialize"] } to { version = ">=0.23", features = ["auto-initialize"] }.
  • Updated serde from { version = "1.0.190", features = ["derive"] } to { version = ">=1.0", features = ["derive"] }.
  • Updated serde_json from "1.0.108" to ">=1.0".

Rationale:

• Flexibility: Allowing versions greater than or equal to the specified minimum enables compatibility with newer releases and patch updates without forcing an immediate version bump across the board.
• Ease of Maintenance: This approach minimizes potential dependency conflicts, especially for downstream users who might already be using newer versions of pyo3 or serde.

Impact:

• The changes are limited to version specification in Cargo.toml and should not affect the API or functionality.
• All tests are expected to pass as long as the newer versions remain backwards compatible.

Additionally, I check what the minimum supported pyo3 version is and it is 0.23.0.

Please review and let me know if further adjustments are needed.

[LockedThread]

@konn Please review.

[termoshtt]

Since serde = "1.0.190" means 1.0.190 <= version < 2.0.0 (not < 1.1), this change only allows 1.0.189 or older. There is no reason to use old patch version. This change is not acceptable.

[LockedThread]

I agree there are very few reasons to use old patch versions. I decided to loosen the serde dependency after looking at my dependency tree and realizing my binary was using 10 different versions of serde. This is caused by libraries having strict versions.

[LockedThread]

Additionally, at the very least we should increase the pyo3 bounds to <0.26.0 since the release of 0.25.0, in preparation of 0.25.1 being released.