Move encryption and decryption configuration options into a separate crypto namespace

[adamreeve]

This moves the file_encryption_properties and file_decryption_properties configuration options out of the global Parquet options and into a new config field inside TableParquetOptions.

This allows using :: as the separator for column specific keys and metadata by avoiding the conflict with the logic for TableParquetOptions::column_specific_options, and means we can make use of the config_namespace_with_hashmap macro to simplify the ConfigField implementations.

It also simplifies the reading configuration by allowing encryption options to be set in the ParquetReadOptions rather than needing to modify the session state.

I think this also makes more sense conceptually, as these options are likely to be table/file specific rather than something you'd want to set for a whole session.

[adamreeve]

This is something I wasn't 100% sure about. Should this use FileDecryptionProperties or ConfigFileDecryptionProperties? Given this doesn't need to be serializable here it seemed nicer to just use FileDecryptionProperties from the Parquet crate. Later in to_listing_options these get converted to ConfigFileDecryptionProperties though.

I'm concerned that this might be a bit misleading to users who could expect to be able to use any FileDecryptionProperties instance here, but this won't work if the decryption properties use a key retriever as that will be lost when converting to ConfigFileDecryptionProperties.

I think that's probably OK as long as this is well documented and results in a helpful error message if misused.