AWS::Glue::Database - CatalogId should not be required

1. AWS::Glue::Database-CatalogId
2. [CatalogId is not required in the API](https://docs.aws.amazon.com/glue/latest/dg/aws-glue-api-catalog-databases.html#aws-glue-api-catalog-databases-CreateDatabase), so it shouldn't be required in the CloudFormation resource
3. Expected behavior -> CloudFormation shouldn't pass the CatalogId if it's not provided by the user, and Glue will default it to the account ID
4. Test case recommendation (optional) ->
5. Links to existing API doc (optional) -> https://docs.aws.amazon.com/glue/latest/dg/aws-glue-api-catalog-databases.html#aws-glue-api-catalog-databases-CreateDatabase
6. Category tag (optional) -> Analytics
7. Any additional context (optional)

Start with the AWS::Glue::Database resource definition and compare its CatalogId handling with the linked Glue CreateDatabase API documentation. Verify the behavior when users omit CatalogId, and add or update a test showing that CloudFormation does not pass it and Glue defaults it to the account ID.

Written by the indexing model from the issue text.