This PR adds a '/api/markings' endpoint, where basic CRUD operations can be applied to the markings records. An important note is that the create and update routes are using the unchecked data type at this time. This means that foreign keys, such as critter_id or any other marking related IDs in the markings table do not have rules enforced, so any valid uuid could be provided to these fields, even if they do not exist in their respective table. This should probably be validated more strictly once the scope for this endpoint is more well-defined.
This PR adds a '/api/markings' endpoint, where basic CRUD operations can be applied to the markings records. An important note is that the create and update routes are using the unchecked data type at this time. This means that foreign keys, such as critter_id or any other marking related IDs in the markings table do not have rules enforced, so any valid uuid could be provided to these fields, even if they do not exist in their respective table. This should probably be validated more strictly once the scope for this endpoint is more well-defined.