Release/0.7.0

[Swandog]

Bumped versions, filled out the changelogs, and updated the citation

[Swandog]

Note: I didn't change the version of lace_consts since the only change in it was a PATCH version bump in the rv dependency. I think that shouldn't require publishing a new version since Cargo should do the right thing and update the patch by default when people build it.

[schmidmt]

It all looks good. Should we write a tool to check the versions to ensure they're all in sync?

[Swandog]

It all looks good. Should we write a tool to check the versions to ensure they're all in sync?

The versions of the Rust subcrates should not be in sync with each other (we discussed this awhile back and Bax made the executive decision to not sync them)
Cargo will already fail if the dependency specifications do not reference the correct version (e.g., when I bumped lace_utils to 0.3.0, cargo check failed for the crates (like lace) that depended on it until I bumped their dependency specification to 0.3.0)
The Rust and Python crates do not need to be synced with each other, as per discussion with Bax earlier
The pylace/Cargo.toml and pylace/pyproject.toml versions DO need to be in sync with each other and there is already a step checking that in the release process