JSON and Spatial types need to be considered strings

[mng1dev]

Problem

Json and spatial columns are sent as string record, but defined as object type in the catalog.
This causes a problem because targets expect an object record and not a string.

More details in #99

Proposed changes

The columns of JSON and Spatial types are defined with type ["null", "string"] in the catalog.

Types of changes

What types of changes does your code introduce to PipelineWise?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• Description above provides context of the change
• I have added tests that prove my fix is effective or that my feature works
• Unit tests for changes (not needed for documentation changes)
• CI checks pass with my changes
• Bumping version in setup.py is an individual PR and not mixed with feature or bugfix PRs
• Commit message/PR title starts with [AP-NNNN] (if applicable. AP-NNNN = JIRA ID)
• Branch name starts with AP-NNN (if applicable. AP-NNN = JIRA ID)
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions

[Samira-El]

Hi Vektor, thanks for the PR, the change makes sense to me.

The CI is failing, can you please cover this change with some extra unit/integration tests.

[ile-g]

Hi team. It would be great to have this fix in.
The PR seems stale - can I help unblock this?