Update output data validations for frames and ctf

[manasaV3]

Relates to: #1418

Rationale

This feature expects the source data to have the required related entities before it can be ingested to surface the frames and ctf metadata. To ensure that the source data is in a valid state, we need to add a validation step that can determine if the data is accurate before the ingestion.

Tasks

Validations for MDOC/Frames

1. number of mdoc sections == number of frame files on s3 == number of items in frames table/metadata
2. frame file names match file names in mdoc section
3. tilt axis angle in mdoc file matches that in tilt series metadata (+/- 10 deg)
4. tilt axis angle in mdoc file matches that in the alignment metadata [PSAP.rotation_angle] (+/- 10 deg)
5. number of frames >= # of per section parameters

Validations for Frames Metadata

1. When isGainCorrected == False, a Gains entity exists for the run
2. max(acquisitionOrder) < number of frames - 1
3. Sum of exposureDose of all frames associated with a tilt series == totalFlux of tilt series
4. Sorting acquisitionOrder low-to-high and accumulatedDose low-to-high results in the same order

Validations for PerSectionParameter Metadata

1. -180 <= astigmaticAngle <= 180
2. majorDefocus > minorDefocus
3. 0 <= phaseShift <= 2*pi
4. maxResolution > 0
5. rawAngle matches mdoc angle as defined above
6. 0 <= zIndex <= (z-Dimension of tilt series - 1)

What Done Looks Like?

The existing validation tests include the new tests. We are able to run validation for any standardized data from command line or in the batch environment.