[Pkg-rust-maintainers] Bug#1124657: rust-rusqlite: please upgrade to v0.37

[Peter Green]

> Please upgrade crate rusqlite to v0.37.

I've taken a preliminary look through the rdeps amd they seem quite spread out, but the most
important ones seem to have updated.

libchewing - dependency has no upper limit - testing needed.
meli - broken and not in testing
ripgrep-all - latest upstream uses 0.30, Debian package seems to upgrade to 0.32 and downgrade again?!
rust-cargo - upstream version in Debian uses 0.36, upstream git uses 0.39, no code changes when upgrading, but one cargo feature change https://github.com/rust-lang/cargo/commit/314367b398bff11893fd844d3f1f7665b65c35ec
rust-erbium-core - upstream allows versions 0.28 to 0.37 inclusive
rust-inquest - upstream allows versions 0.29 to 0.39 inclusive
rust-parsec-service - still uses 0.29 upstream
rust-sequoia-cert-store - upstream allows versions 0.29 to 0.39 inclusive
rust-sequoia-chameleon-gnupg - latest upstream release allows versions 0.29 to 0.31 inclusive, upstream git  allows versions 0.29 to 0.39 inclusive, upstream made no code changes when relaxing the dependency
rust-sequoia-octopus-librnp - latest upstream release allows versions 0.24 to 0.31 inclusive, upstream git is the same
rust-sequoia-sq - latest upstream release allows versions 0.24 to 0.32 inclusive, upstream git is the same
rust-taskchampion - latest upstream uses 0.37 but is semver breaking, upstream git uses 0.39, upstream made no code changes when updating but did make a change to enabled featureshttps://github.com/GothenburgBitFactory/taskchampion/commit/e35105e45a040113004a356046a24a467b23436b
rust-tokio-rusqlite - latest upstream uses 0.37, has a minor semver bump which we may as well take as part of this update
settle - still on 0.29 upstream

IMO we should try preparing an update to the latest version (0.39)
and only look at lower versions if that proves impractical.

Anyone else have any thoughts?