Fix to disallow additional properties in nested fields, eg, constraints

[george42-ctds]

The current fields-level specification of

"additionalProperties": false,

applies to a single level in our version of jsonschema. In newer versions the specification automatically applies to nested levels. In our version it does not apply to sub-levels such as constraints.

In the above, additionalProperties means any properties present in the file that are not part of the schema.

Additional properties under constraints are not checked in the validation process. They simply get passed through in the extraction process. A file with constraints.enumLabels and constraints.foo does not raise an error. The columns get passed through and they appear in converted files.

If we want to disallow any additionalProperties in sub-levels (eg, constraints, StandardMappings) then we need to insert specifications in the sub-levels.

This branch has additional specifications in the sub-levels in the schema for json. Files with constraints.enumLabels and constraints.foo will raise an error and will not generate converted output files.

New Features

Breaking Changes

Bug Fixes

• Explicitly disallow additional properties under nested fields

Improvements

Dependency updates

Deployment changes

[github-actions]

The style in this PR agrees with black. ✔️

This formatting comment was generated automatically by a script in uc-cdis/wool.