fix(deps): pin dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
anyhow	dependencies	pin	1.0.64 → =1.0.103
clap	dependencies	pin	3.2.20 → =3.2.25
colored	dependencies	pin	2.0.0 → =2.2.0
ctrlc	dependencies	pin	3.2.4 → =3.5.2
glob	dependencies	pin	0.3.0 → =0.3.3
lazy_static	dependencies	pin	1.4.0 → =1.5.0
log	dependencies	pin	0.4.17 → =0.4.33
nix	dependencies	pin	0.26.1 → =0.26.4
pretty_env_logger	dependencies	pin	0.4.0 → =0.4.0
rand (source)	dependencies	pin	0.8.5 → =0.8.6
regex	dependencies	pin	1 → =1.12.4
reqwest	dependencies	pin	0.11.14 → =0.11.27
semver	dependencies	pin	1.0.13 → =1.0.28
serde (source)	dependencies	pin	1.0.144 → =1.0.228
serde_json	dependencies	pin	1.0 → =1.0.150
strsim	dependencies	pin	0.10.0 → =0.10.0
toml	dependencies	pin	0.5.9 → =0.5.11

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.