Consider if we need to support turning off schema validation

[eladb]

In the discussion on #606, @ccurrie-amzn proposed that L1 resources will support turning off schema validation, in case the resource's CloudFormation schema is not up-to-date and there's a desire to use the strongly-typed property overrides nevertheless.

The current "escape hatch" for this use case (based on the design in #606) is to use addPropertyOverride which is weakly-typed.

We should collect user feedback to understand how much turning off validation is needed. It's non trivial to implement since the generated L1 resources have mappers that convert javascript-style properties to CloudFormation-style and those are dependent on the knowledge of the schema (if there's an array we map all elements, etc).

Furthermore, disabling schema validation is by definition limited when using the strong-typed overrides because the compiler/type-checker will perform much of the validation anyway (i.e. required/optional values, etc), and in some languages those are impossible to "turn off".

We suspect that addPropertyOverride, which bypasses validation, would be sufficient for such use cases, but we will track via this issue.

[eladb]

I am closing this for now. Let's reopen if this comes up again