Support the AES-GCM-CTR-V1 encryption algorithm for Parquet modular encryption

[adamreeve]

Follow up task to #6637, which adds read support for files that use Parquet modular encryption.

Currently only the AES-GCM-V1 algorithm is supported. AES-GCM-CTR-V1 requires using un-authenticated AES-CTR for data pages, which isn't yet supported by the Ring library.

There's a Ring issue open for this and the maintainer has expressed that they'd be open to accepting this feature but it isn't planned: briansmith/ring#414

For details on the two algorithms, see https://github.com/apache/parquet-format/blob/master/Encryption.md#42-parquet-encryption-algorithms.

[adamreeve]

Ring is now in "security maintenance only" mode under new maintainers, so contributing plain CTR might not be possible, see https://rustsec.org/advisories/RUSTSEC-2025-0007.html and briansmith/ring#2414.

We may want to look at alternatives like aws-lc-rs, although that has less platform support which may be a problem (eg. no wasm support). It looks like there's already AES-CTR support in aws-lc-rs though: https://docs.rs/aws-lc-rs/1.12.6/aws_lc_rs/cipher/index.html. Plus support for 192 bit keys which is missing from Ring but supported by the Parquet format: https://docs.rs/aws-lc-rs/1.12.6/aws_lc_rs/aead/constant.AES_192_GCM.html

If we end up contributing AES-CTR support to Ring, it might make sense to try to match the aws-lc-rs API, as asws-lc-rs tries to mostly be API compatible with Ring.