Revert "chore: explicity set cargo feature resolver version to 2"

[etungsten]

cargo make build-package breaks due to this change. This needs re-evaluating.
This reverts commit 3a4dadc.

Issue number:
#3372

Description of changes:

    Revert "chore: explicity set cargo feature resolver version to 2"
    
    `cargo make build-package` breaks due to this change. This needs
    re-evaluating.
    This reverts commit 3a4dadc3c9e10a2ed2eac76377c1643bb71a29c5.

Testing done:
cargo make build-package works:

[cargo-make][1] INFO - Running Task: build-package                                                                                                                                                                 
   Compiling glibc v0.1.0 (/home/fedora/bottlerocket/packages/glibc)                                                                                                                                               
   Compiling os v0.1.0 (/home/fedora/bottlerocket/packages/os)                                                                                                                                                     
    Finished dev [optimized] target(s) in 3m 38s                                                                                                                                                                   
[cargo-make][1] INFO - Build Done in 294.04 seconds.                                                     
[cargo-make] INFO - Build Done in 294.54 seconds.    

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.

[foersleo]

I think for the time being reverting this is the right decision. Looking at the analysis Markus did on the ticket I raised it seems making this work with resolver 2 may be a bigger effort.

[stmcginnis]

I agree. This is just a warning with the newer toolchain, so it's not that big of a deal. We will likely need to sort it out before that warning becomes an error, but I would assume we have some time before that is a possibility.

[markusboehme]

I was hoping someone would have a quick idea, but reverting works for now, too. Thanks!