feat: s3 data validation: cross checking tiltseries & frames files

[daniel-ji]

Merge after #223.

See the Tilts & RawTilts & Angles Cross Checks section of https://docs.google.com/document/d/1yMKM0DW9KRhlcYiBGPcR7oW0liGtUew6NAmBhMg5U3w/edit.

Documentation from the code:

    """
    A class to test tilt angle data. Only checking that the # of angles in these files are consistent with other files / 
    data and that they properly map to other files / data. Other data validation tests is done in respective classes.
    Spans .tlt, .rawtlt, .mdoc, tiltseries_metadata.json, frames files.
    Ordering:
        - .tlt (<=) maps to .rawtlt (not necessarily 1:1)
        - .rawtlt (<=) maps to .mdoc (not necessarily 1:1)
        - .mdoc (==) one-to-one with frames files & tiltseries_metadata size["z"]
        - tiltseries metadata size["z"] == frames_count == # of frames files

    Extra test redundancy is added for the cases where files sometimes do not exist.
    Extra redundancy tests are done on the tiltseries metadata size["z"] since frames_count / # of frames files may be 0
        when no frames are present and that is a valid case. To ensure consistency, we rely on the check
        tiltseries metadata size["z"] == frames_count == # of frames files.
    """

[manasaV3]

This might not always hold true, as there is a possibility of frames that were generated not being used for the tiltseries.

[daniel-ji]

Sounds good, I'll remove all the max_frames_count checks in this PR and the future ones.

[manasaV3]

The comments documenting the tests are really helpful. 🔥