CDK: make TypeTransformer more robust to incorrect incoming records

[grubberr]

Signed-off-by: Sergey Chvalyuk grubberr@gmail.com

What

Try to fix
https://github.com/airbytehq/alpha-beta-issues/issues/222
#15405

There are cases which can kill transformer by exceptions, for example:

schema = {
    "type": "object",
    "properties": {
        "value": {
            "type": "array",
            "items": {"type": "string"}
        }
    }
}

record = {"value": {"key": "value"}}
TypeTransformer(TransformConfig.DefaultSchemaNormalization).transform(record, schema)

RuntimeError: dictionary changed size during iteration

Schema assume that "value" has to be array of strings, but we get sub-object.
In such cases transformer has to generate warning message, leave record as is and not be killed.

How

When we process "array" just make sure that instance variable of type list
if it's not list just skip it, we can do nothing in such cases.

[brianjlai]

Changes seem pretty straightforward, but can you add some additional context to the PR description as to which connector you were upgrading and what exactly triggered the need for this change to the CDK?

[sherifnada]

Can you add the comment you added in the PR description as a source code comment to clarify for the next developer reading this why we verify the isinstance?

[grubberr]

/publish-cdk dry-run=true

🕑 https://github.com/airbytehq/airbyte/actions/runs/3042879452
✅ https://github.com/airbytehq/airbyte/actions/runs/3042879452

[grubberr]

/publish-cdk dry-run=false

🕑 https://github.com/airbytehq/airbyte/actions/runs/3043056678
✅ https://github.com/airbytehq/airbyte/actions/runs/3043056678