ci: fix cargo-release version interpolation

[conorsch]

Describe your changes

Updates the package metadata for the parameter-setup crate, which was recently pulled into the workspace. Without these changes, cargo-release was failing to add a version number to the automatically generated commit message.

Issue ticket number and link

Refs #4928, #4930.

Testing and review

If you care to verify the results locally, you can:

git checkout -b my-feature-branch
cargo release 0.80.9 --execute # this won't push anything, but will require cleanup
git show # to view the commit message

Make sure that the generated commit message says "chore: release version 0.80.9", not "chore: release version {{version}}". If you ran these steps, you must clean up:

git checkout main
git tag -d v0.80.9
git branch -D my-feature-branch

If you forget to delete the tag, then when 0.80.9 is actually released, you won't be able to pull the tag from github.

Checklist before requesting a review

• I have added guiding text to explain how a reviewer should test these changes.

• If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

  package metadata only, no changes to application code

[redshiftzero]

LGTM

[redshiftzero]

ah, sorry about that!

[conorsch]

Initially I tried to set the version to 0.80.8 explicit, but that didn't resolve the problem. Needed to set version = { workspace = true } and then things were happy again.