Ceramic SDK performs client-side schema validation

[mzkrasner]

The ModelInstanceClient does not currently make use of some existing schema validation utilities found in model-instance-handler package that perform schema validation (checking against field constraints, etc). Additionally, better integrating this package into the ModelInstanceClient will make the package more ergonomic and easy to work with, reducing boilerplate code for users.

At current state, users can manually combine methods from these separate packages. Resolution of this issue would make this disparate functionality generally easier to work with for users.

[m0ar]

@mzkrasner (cc @nathanielc) can you explain how this relates to ceramicnetwork/rust-ceramic#663 ? Is it the validation of linked/relation models at time of querying?

[nathanielc]

This is about doing client side validation in addition to the server side validation in the linked PR. However this is not a priority, rather there was a partial implementation of client side validation in the SDK previously, but as it was only partial and had significant performance issues we removed it. This issue is a reminder to revisit that concept in the future.

In short, validation is best server side and that is where it lives now.