Update Cargo.lock to reflect version 0.1.1

[Copilot]

Problem

The publish workflow was failing at the verification step because the Cargo.lock file contained outdated version entries (0.1.0) while the Cargo.toml files had been updated to version 0.1.1. When the workflow runs with the --locked flag, Cargo requires exact version matches between the lock file and manifest files.

Solution

Updated Cargo.lock to synchronize the package versions with Cargo.toml:

• comtains: 0.1.0 → 0.1.1
• comtains_macros: 0.1.0 → 0.1.1

This was accomplished by running cargo update --workspace, which updates the lock file to reflect the current package versions without changing any dependencies.

Verification

All publish workflow checks now pass successfully:

• ✅ cargo check --workspace --locked
• ✅ cargo test --workspace --locked (all 9 tests pass)
• ✅ cargo clippy --workspace --all-targets --locked (no warnings)
• ✅ cargo package --locked -p comtains_macros
• ✅ cargo package --locked

The publish workflow should now complete successfully without verification errors.

Original prompt

update the cargo.lock as the action for publishing fails at the verification step...

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.