Update dependencies (#178)

## Description

### Why is this change being made?

1. Addressing CVEs on dependencies


### What is changing?

1. Dependency version numbers in the lockfile


### Related Links
- **Issue #, if available**:

---

## Testing

### How was this tested?

1. `cargo test --exclude integration_tests --workspace`

### When testing locally, provide testing artifact(s):

1. 

---

## Reviewee Checklist

**Update the checklist after submitting the PR**

- [x] I have reviewed, tested and understand all changes
  *If not, why:*
- [x] I have filled out the Description and Testing sections above
  *If not, why:*
- [x] Build and Unit tests are passing
  *If not, why:*
- [x] Unit test coverage check is passing
  *If not, why:*
- [ ] Integration tests pass locally
*If not, why:* Did not run integ tests locally, will wait for GH action
run.
- [ ] I have updated integration tests (if needed)
*If not, why:* Not needed since this is just a dependency version
update.
- [ ] I have ensured no sensitive information is leaking (i.e., no
logging of sensitive fields, or otherwise)
  *If not, why:* Not applicable, we are just doing dependency update.
- [ ] I have added explanatory comments for complex logic, new
classes/methods and new tests
  *If not, why:* No complex logic added.
- [ ] I have updated README/documentation (if needed)
  *If not, why:* No changes to readme needed for a version update.
- [ ] I have clearly called out breaking changes (if any)
  *If not, why:* No breaking changes.

---

## Reviewer Checklist

**All reviewers please ensure the following are true before reviewing:**

- Reviewee checklist has been accurately filled out
- Code changes align with stated purpose in description
- Test coverage adequately validates the changes

---

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

Author: simonmarty