Consider switching to clap 4.x

[cr-tk]

aws-nitro-enclaves-image-format currently still depends on clap 3.2.x, which pulls in the unmaintained atty crate as a transitive dependency. This gets flagged by dependabot on downstream projects.
See https://rustsec.org/advisories/RUSTSEC-2024-0375 and https://rustsec.org/advisories/RUSTSEC-2021-0145 for context.

To resolve this, a switch to a newer clap 4.x branch is needed, which drops atty as a dependency. Dependabot created the PR #37 , but it seems that API changes in clap need to be resolved by the maintainers.

Other AWS nitro enclave crates resolved this already, see for example aws/aws-nitro-enclaves-cli@6245dbc .

[cr-tk]

@atanzu thank you for creating #45, which will fix this issue by switching to clap 4.4. However, it appears that the review of the PR has stalled for over half a year now.

AWS Nitro is advertised for highly sensitive workloads. The corresponding software should not depend on known-unmaintained dependencies.

[cr-tk]

#45 has been successfully merged. The change I'm seeing is two-fold: going from clap 3.2 -> clap 4.4 for the eif_build crate with the CLI tool, and dropping clap completely for aws-nitro-enclaves-image-format itself.
I see that some partially related maintenance and MSRV update work also landed through #48 after problems being mentioned in #47.

A new release with these changes would complete this GitHub issue 👍