Library: improve debugging for untyped languages and incorrect naming

[DanielMSchmidt]

Description

In languages like Python where there are no strong types users with invalid configuration (e.g. camel cased vs snake cased attribute keys) might not spot their mistake if they are new to CDKTF and perceive the behaviour as a bug.

We can (potentially) look out for some common mistakes like wrong casing, passing an array instead of an item of the list, etc and throw more helpful errors. This might need to be done in JSII

References

No response

Help Wanted

• I'm interested in contributing a fix myself

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[DanielMSchmidt]

See also #1898