Provide Type Constraints Consistent With AWS

It may be hard, but it'd be great to have as many [type constraints](https://pkl-lang.org/main/current/language-reference/index.html#type-constraints) as possible to avoid errors like:
```
CodeCommitRepository: The repository name is not valid. Repository names can be any valid combination of letters,
numbers, periods, underscores, and dashes between 1 and 100 characters in length. Names are case sensitive. For more
information, see Limits in the AWS CodeCommit User Guide.
```

Start with the linked Pkl type-constraints documentation and the AWS CodeCommitRepository validation example in the issue. Determine which AWS constraints should be represented and how broad the requested coverage is. Done means the project provides as many consistent AWS-aligned type constraints as the agreed scope requires.

Written by the indexing model from the issue text.