Release data validation code

[djkapner]

During the release process for v1.0.0/v1.0.1 of the VB2P dataset, we learned some consistency checks from Marina that the release data should meet:

In the final dataset where all experiments and containers are passing:

- A mouse should have <=8 containers
- A session should have <=8 containers
- A session should have <=8 experiments
- A container should have >=4 experiments
- the imaging_depth for all experiments in a container should fall within a 30um range of each other
- for VisualBehaviorMultiscope, each targeted_structure should have <=4 containers
- for VisualBehaviorMultiscope4areasx2d, each targeted_structure should have <=2 containers

I have started some code to check these things, and to also check the generated metadata against the metadata stored in the BehaviorSession.from_lims() and BehaviorOphysExperiment.from_lims() objects so that we can be sure the metadata csvs are consistent with the published data.

Tasks:

• [ ] finish this code, incorporate it into AllenSDK behavior_project_cache/external
• [ ] run the code on the same data released as v1.0.1
• [ ] review inconsistencies with the science team.
• [ ] make plan for corrected release, if applicable.