move to ultra restrictive schema

[kilojoules]

This makes our YAML reader default to additionalProperties: false. This avoids ambiguities when validating encoded data.

[rafmudaf]

@kilojoules heads up the tests are failing here

[bayc]

@kilojoules I agree that we should update parameters to not allow additional properties to aid in validation, but I am hesitant to apply a blanket function like this, but would rather explicitly add to each current and new definition the correct property to prevent additional properties. A blanket function like above also restricts us from allowing custom cases for definitions, which is another discussion to have.

[kilojoules]

@bayc My experience is that this creates a huge amount of clutter and it is easy to miss a specification of additional properties false. Iwould instead suggest explicitly stating when additional properties is true. This seems like a strong safeguard against typos.