Update AWS nitro crates and deps for qos_enclave

[cr-tk]

Summary & Motivation (Problem vs. Solution)

AWS has recently announced GHSA-g59m-gf8j-gjf5 which classifies a recent improvement in their API across in many of their Rust SDK crates as a security patch. This is a motivation to adopt newer versions of the AWS SDK crates that we use for qos_enclave.

At the time of writing, we can not switch aws-sdk-kms to a new enough version since other AWS crates such as aws-nitro-enclaves-image-format explicitly require use of older versions, see aws/aws-nitro-enclaves-image-format#49.

Additional restrictions on aws-config version ranges, combined with cargo restrictions on allowed parallel usage of different major versions of the same crate (such as aws-types 1.1.9 and 1.3.11) unfortunately make it difficult for us to adopt the newer versions.
For example, our tests build with aws-types 0.101.0 but then fail with

the trait aws_config::meta::region::ProvideRegion is not implemented for aws_types::region::Region

during runtime, and newer 1.0.x or 1.1.x versions aren't allowed due to the previously mentioned cargo rules. This holds back what this PR can currently do.

The aws-nitro-enclaves-image-format development has finally dropped atty as a transitive dependency, allowing us to get rid of it and the related security warnings (unmaintained crate) as described in aws/aws-nitro-enclaves-image-format#44 . Since there's no official release for that yet, we have to use the Cargo patch mechanism as a workaround to enforce this. https://github.com/advisories/GHSA-g98v-hv3f-hcf is also related, but not relevant for us.

How I Tested These Changes

CI

[cr-tk]

The situation unfortunately hasn't improved since the AWS crates and repositories have not been updated to be compatible with patched versions.

[cr-tk]

Updated the nitro-cli pin from 1.4.4 to 1.4.5. Unfortunately, this doesn't change the overall situation regarding the other AWS crates.

Given the partial improvement for some transitive dependencies, I think we should go forward with merging this now, to get the partial benefits that are reachable now.

Note that the new nitro-cli version required bumping the MSRV of qos_enclave from 1.88 to 1.92, but this is below our current 1.94 tooling level and should be okay.