Refactor core file validators based on aind-data-schema-models expected modalities

[dbirman]

User story

As a user I want to be able to build valid models that include only the subset of files required for a particular set of modalities. The Metadata validation code should check that I've attached all the required files and skipped any files that are excluded by all the modalities in my data asset.

Acceptance criteria

• model_validator that ensures that Metadata models have all required files and no files excluded by all of the data's modalities

Sprint Ready Checklist

• 1. Acceptance criteria defined
• 2. Team understands acceptance criteria
• 3. Team has defined solution / steps to satisfy acceptance criteria
• 4. Acceptance criteria is verifiable / testable
• 5. External / 3rd Party dependencies identified
• 6. Ticket is prioritized and sized

Notes

Getting the combination of required/excluded files for a set of modalities could be a convenience function that we stash in utils here or in aind-data-schema-models

[dbirman]

Waiting on AllenNeuralDynamics/aind-data-schema-models#76