Batching should complain when cohort has been changed vs last extraction [Magalie]

[tznind]

Is your feature request related to a problem? Please describe.
When performing a large batched extraction. I get half way through then realise I have the wrong cohort. I change the cohort and run the extraction the rest of the way.

This currently results in:

• Half of your file having one cohort
• Second half of your file having the new cohort

Describe the solution you'd like
When Extraction is a batch resume it should check the extraction logs to determine if the cohort has changed and complain if it has. ProposedFix for CheckResult may be 'to reset progress to null (resetting batching)'.