Upgrade to newer aws-nitro-enclaves-cli

[cr-tk]

Summary & Motivation (Problem vs. Solution)

We rely on several AWS NSM crates. After a long break, AWS released a new version of aws-nitro-enclaves-cli that we should adopt, see here for changelog information.

Along the way

• update the aws-nitro-enclaves-nsm-api, which is basically just a MSRV update
• harmonize the libc minimum version, which doesn't change any Cargo.lock entries

These changes move us closer to getting rid of the unmaintained atty crate, which is now removed in most places through a switch to clap 4.x that doesn't depend on it anymore. Unfortunately, one usage site remains with aws-nitro-enclaves-image-format, which still depends on clap 3.x even in a recent version.

The dependency changes bring a lot of review tasks:

review tasks: 40 crates, of which 23 are full and 17 are partial

17 of the completely new crates are aws-* crates, which helps a bit to establish trustworthiness.
At the moment, aws-nitro-enclaves-cli doesn't have Cargo features we can disable, so this dependency load is hard to reduce from my perspective.

How I Tested These Changes

Local unit tests.

This change needs thorough testing in various testing environments.

Pre merge check list

• Update CHANGELOG.MD

[cr-tk]

Rebased on top of the now-merged #504 to fix build problems. Ready for review - still working on the build problems.

[cr-tk]

CI issues are resolved. I'm working on the dependency security review.

[cr-tk]

The dependency security review is complete (see internal documentation) and this PR is ready to merge.

[r-n-o]

All of it looks reasonable. My only point of concern is utf8parse. I can't find a trusted source for it.

[r-n-o]

The utf8parse mystery is solved, it was removed from https://github.com/alacritty/vte in https://github.com/alacritty/vte/pull/118/files. The exact source for 0.2.2 is available at https://docs.rs/crate/utf8parse/0.2.2/source/Cargo.toml -> all good ✅

[cr-tk]

@r-n-o as commented inline, some of the new-appearing crate entries in src/qos_enclave/Cargo.lock actually weren't new at all, since they were already in the main src/Cargo.lock before this PR. This is a side effect of workspace/lockfile mechanics, where the qos_enclave crate essentially uses a subset of dependency entries from the workspace.
As far as I can see, this fully explains why some apparently changed crates weren't part of the review list.

It's still useful that you had a look at them, good sanity checking!
Thank you for the additional review 👍