AWS: add DynamoDb catalog

[jackye1995]

Add DynamoDB catalog implementation, with the following specifications:

1. identifier column (partition key): table identifier string, or NAMESPACE for namespaces
2. namespace column (sort key): namespace string
3. a global secondary index (GSI) with namespace as partition key, identifier as sort key, no other projected columns
4. version column : UUID string, used for optimistic locking
5. updated_at column : timestamp long, used to record latest update time
6. created_at column : timestamp long, used to record initial create time
7. p.[property_key] column : string, used to store properties (namespace property or Iceberg-defined table properties including table_type, metadata_location and previous_metadata_location)

This design has the following benefits:

1. table name is used directly as partition key to avoid any potential hot partition issue, comparing to use namespace as partition key and table name as sort key
2. namespace operations are clustered in a single partition to avoid affecting table commit operations
3. a reverse GSI is used for list table operation, and all other operations are single row ops or single partition query. No full table scan is needed for any operation in the catalog.
4. a string UUID version field is used instead of updated_at to avoid 2 processes committing at the same millisecond
5. multi-row transaction is used for renameTable to ensure idempotency
6. properties are flattened as top level columns so that user can add custom GSI on any property field.

Limitations:

1. To avoid complications in parsing namespace, dot (.) is not allowed in any level of namespace
2. Similarly, to avoid complications in parsing table identifier, dot is not allowed in table name.

@yyanyy @rdblue @SreeramGarlapati @johnclara @danielcweeks

[jackye1995]

@danielcweeks any additional comments?

[danielcweeks]

This looks good to me. Just the two small updates (docs and empty line) and I'm happy to commit.

[jackye1995]

@danielcweeks thank you, updated!