Description
Tracking issue: Can be closed once we have migrated all errors and have enabled the eslint-rule to enforce typed errors.
Currently all errors thrown by the AWS CDK in aws-cdk-lib etc are regular untyped Errors. That makes it difficult for a caller to distinguish between errors thrown intentionally by the construct library, and other errors like coding bugs etc.
The CDK should only throw well typed errors.
All errors should be categorized into the type of error they are (most are going to be validation errors).
We should enforce this by writing an eslint rule.