Update dependencies for 3.1.0

[farost]

Usage and product changes

Update dependencies prior to release 3.1.0. In details:

• Update dependencies without pinned versions.
• Update the rocksdb crate
• Pin the version of the cc create to avoid breaking rocksdb Bazel build.

Motivation

Make sure that the dependencies are in a stable and non-conflicting state

Implementation

See comments.

[typedb-bot]

PR Review Checklist

Do not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed.

---

Trivial Change

• This change is trivial and does not require a code or architecture review.

Code

• Packages, classes, and methods have a single domain of responsibility.
• Packages, classes, and methods are grouped into cohesive and consistent domain model.
• The code is canonical and the minimum required to achieve the goal.
• Modules, libraries, and APIs are easy to use, robust (foolproof and not errorprone), and tested.
• Logic and naming has clear narrative that communicates the accurate intent and responsibility of each module (e.g. method, class, etc.).
• The code is algorithmically efficient and scalable for the whole application.

Architecture

• Any required refactoring is completed, and the architecture does not introduce technical debt incidentally.
• Any required build and release automations are updated and/or implemented.
• Any new components follows a consistent style with respect to the pre-existing codebase.
• The architecture intuitively reflects the application domain, and is easy to understand.
• The architecture has a well-defined hierarchy of encapsulated components.
• The architecture is extensible and scalable.

[farost]

Rocksdb 0.23.0 introduced bindgen-runtime and bindgen-static. bindgen-runtime used to be the only and the default option, and bindgen-static did not exist. Now, by using default_features, we turn off bindgen-runtime, and we don't have bindgen at all... Weird. So we turn on this feature explicitly.

[farost]

It's not necessary to update it now, but since we discovered and solved this upgrade issue, I think it's valuable to grab it.

[flyingsilverfin]

agree

[farost]

We pin the cc version. [email protected] (which is updated implicitly by a single deps update run) changes something so librocksdb_sys starts having issues with build through Bazel, throwing C++-related errors (probably due to incorrectly used C++17). It was discussed in Discord: https://discord.com/channels/665254494820368395/672580553677078548/1346804418489618443

We do suspect that something got broken in rust-lang/cc-rs#1403, but it does not affect cargo build. Since we don't see a problem in pinning the version of the crate (discussed in the same Discord channel), we decided to do so in the end.