feat(ingest/jsonschema) enable schema-aware JsonSchemaTranslator

[KulykDmytro]

Changes

Picking up schema-validator class based on one defined in schema instead of using Draft7 everywhere

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

closes #8970

[hsheth2]

@KulykDmytro not super familiar with the jsonschema library - what exactly does this do?

[KulykDmytro]

@KulykDmytro not super familiar with the jsonschema library - what exactly does this do?

@hsheth2 It handles json-schema operating/validation
BTW datahub is using it underneath but in narrowed way (hardcoding schema Draft to v7)

we faced same issue in our internal projects (validate kafka json data over json schemas) - so proposing solutions we have now.

PS: additionally added some changes description into first post

[hsheth2]

@KulykDmytro oh I see - this is enabling us to detect the jsonschema spec version, and use the appropriate validator