Properly deal with cropping

Right now cropping only impacts block iteration.

A comprehensive block solution would add a data_offset (or similarly named) attribute, so you can store cropped data, but know where it was in the context of the original stack.

Then the SplitDataset could have an apply_crop method that saves such a dataset. the stack_metadata.json fields will have to be extended to support this