Remove indirect dependencies from tools

[stmcginnis]

Issue number:

N/A

Description of changes:

Several tools had indirect dependencies included in their Cargo.toml files. These are pulled in by direct dependencies, so they should not be explicitly included in case those dependencies change and they are no longer needed, or require different versions.

Testing done:

Built each tool and verified no compilation errors.

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

[webern]

This is great. Did you use cargo udeps?

[stmcginnis]

This is great. Did you use cargo udeps?

I actually used cargo machete. I was reading up on some build time optimization and the author called out both tools, but recommended machete since it does not require the nightly toolchain to work. I didn't do a side-by-side comparison of results, but other than some false positives on our relatively linked modules (model, bottlerocket-release) it seemed to catch everything that wasn't being directly used.