[AWS::Glue::Table] - [Coverage] - IntegrationTableProperties

### Name of the resource

AWS::Glue::Table

### Resource name

_No response_

### Description

`IntegrationTableProperties`, which can be created via the CLI command [CreateIntegrationTableProperties](https://docs.aws.amazon.com/glue/latest/webapi/API_CreateIntegrationTableProperties.html), are currently not supported in CloudFormation.

This resource is what enables configuration of Zero-ETL integration [SourceTableConfig](https://docs.aws.amazon.com/glue/latest/webapi/API_CreateIntegrationTableProperties.html#Glue-CreateIntegrationTableProperties-request-SourceTableConfig) and [TargetTableConfig](https://docs.aws.amazon.com/glue/latest/webapi/API_CreateIntegrationTableProperties.html#Glue-CreateIntegrationTableProperties-request-TargetTableConfig), the latter of which is how the `UnnestSpec` property of the integration is set. Without `IntegrationTableProperties`, there is no way to override the default `UnnestSpec` value of `FULL`, which prevents certain valid DynamoDB source tables from being used in Zero-ETL integrations entirely.

### Other Details

https://docs.aws.amazon.com/glue/latest/webapi/API_CreateIntegrationTableProperties.html

Start with the AWS::Glue::Table coverage implementation and the CreateIntegrationTableProperties API documentation linked in the issue. Trace how existing table properties are represented and tested, then support IntegrationTableProperties with SourceTableConfig, TargetTableConfig, and UnnestSpec; done means valid Zero-ETL configurations can override the default UnnestSpec.

Written by the indexing model from the issue text.