chore: forces the protobuf version to be 3.2.0

[kerber0x]

Description and Motivation

This PR forces the protobuf version to be exactly 3.2.0 to avoid issues with other dependencies trying to pull a different (higher) version.

Related Issues

---

Checklist:

• I have read Migaloo's contribution guidelines.
• My pull request has a sound title and description (not something vague like Update index.md)
• All existing and new tests are passing.
• I updated/added relevant documentation.
• The code is formatted properly cargo fmt --all --.
• Clippy doesn't report any issues cargo clippy -- -D warnings.
• I have regenerated the schemas if needed cargo schema.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (35dd827) 94.41% compared to head (c59e36f) 94.41%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #256   +/-   ##
=======================================
  Coverage   94.41%   94.41%           
=======================================
  Files         218      218           
  Lines       24777    24777           
=======================================
  Hits        23393    23393           
  Misses       1384     1384           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[0xFable]

Why does the equal force it, I thought just specifying a dep with a version was enough

[kerber0x]

I thought so too! Apparently omitting it equals ^, which is basically means:

1.2.3 := >=1.2.3, <2.0.0

So the minimum version becomes 3.2.0 in our case, but it can go up to 4.0.0 (excluding). I remember we got issues with protobuf in the past because suddenly some new version appeared. The = forces the crate (and its dependencies) to use that version even if another package could pull a newer version.

See this for reference:
https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-path-dependencies