eslint rules for CDK apps

[rix0rrr]

Describe the feature

We should have a collection of linter rules to help write CDK apps. There are common mistakes that are hard to prevent at runtime, and require static source analysis.

Examples:

• Don't use variable names in construct IDs
• Don't mix L1 and L2 types
• Don't pass scope but pass this

Etc. I'm sure we can come up with more. Put your best ideas in here!

[ashishdhingra]

@rix0rrr Good morning. Please also refer #32136 where user opened a similar feature request.

Thanks,
Ashish