feat: add frozen and locked

[jayy-lmao]

Issue #, if available:

Description of changes:
This introduces the frozen and locked behaviors to cargo chef.
See: https://doc.rust-lang.org/cargo/commands/cargo-build.html#manifest-options

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[atwam]

Hi, just saw this PR as I was about to work on something similar, this time to pass on --verbose to the underlying cargo calls.
@jayy-lmao, if you mind including verbose the same way you have frozen and locked when you fix the comments as per @LukeMathWalker request, that would be great.
If not, no big deal, I'll take inspiration in your PR to submit a PR of my own.

[jayy-lmao]

Hi, just saw this PR as I was about to work on something similar, this time to pass on --verbose to the underlying cargo calls. @jayy-lmao, if you mind including verbose the same way you have frozen and locked when you fix the comments as per @LukeMathWalker request, that would be great. If not, no big deal, I'll take inspiration in your PR to submit a PR of my own.

Just did this now, ty

[vidhanio]

with the addition of these flags, would --frozen become the "default" way to use cargo-chef now? i don't see why someone wouldn't want their ci builds to be frozen and only read from Cargo.lock.

[LukeMathWalker]

It depends—generally speaking, it would probably be alright to make --frozen the default, but it's likely to break some builds and I don't think the benefits outweight the risks here.

[vidhanio]

@LukeMathWalker i meant default more as in "recommended" configuration, like adding it to the README.

[LukeMathWalker]

I don't think it adds enough value and it would probably lead to people using it without understanding what it actually does (because they are copying from the example), which would in turn lead to open issues here.