update-version.sh: Also update versions in Cargo.lock

Currently, the versions in the Cargo.lock file lag behind Cargo.toml (causing cargo to bump them when running a later cargo build) after the update-version.sh script is run. You can see that difference here and here

This is a problem when using cargo build --frozen, such as in a sandboxed build environment without internet access

This change adds a cargo update -w to the script, which only updates workspace deps (effectively doing nothing other than bumping the version numbers in Cargo.lock)