SYS-3868 Update vulnerable cargo.lock dependencies

[nahuseyoum]

Proposed changes

This PR updates vulnerable dependencies found by running cargo audit. There are 5 dependencies identified as vulnerable but unfortunately these require changes to the substrate library to update. Once the substrate upgrade is complete, we can revisit them.

Type of change/Merge

🚨What type of change is this PR?

Put an x in the boxes that apply

• Release
  • Increase versions
  • Baseline tests passed
  • Release type:
    • Major release
    • Minor release
    • Patch release

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR.

• You describe the purpose of the PR, e.g.:
  • What does it do?
  • Highlight what important points reviewers should know about;
  • Indicates if there is something left for follow-up PRs.
• Documentation updated
• Business logic tested successfully
• Verify First, Write Last: In Substrate development, it is important that you always ensure preconditions are met and return errors at the beginning. After these checks have completed, then you may begin the function's computation.

Further comments

[thadouk]

This PR updates vulnerable dependencies found by running cargo audit. There are 5 dependencies identified as vulnerable but unfortunately these require changes to the substrate library to update. Once the substrate upgrade is complete, we can revisit them.

Can you list the packages that were identified?
For example hashbrowns that is updated, the version that was used before was 0.14.3 which is newer than 0.12.3 used now

[nahuseyoum]

This PR updates vulnerable dependencies found by running cargo audit. There are 5 dependencies identified as vulnerable but unfortunately these require changes to the substrate library to update. Once the substrate upgrade is complete, we can revisit them.

Can you list the packages that were identified? For example hashbrowns that is updated, the version that was used before was 0.14.3 which is newer than 0.12.3 used now

@thadouk the list is in the Jira ticket and the fix updates related libraries of the ones that we patched to a common "good" version.