compounding seisflows check parameter errors and point to check statement in source

[bch0w]

Currently when running seisflows check to look at parameter validity (or alternatively running a workflow with seisflows submit), parameter errors are only popped up one by one because hitting the actual assertion error stops the code. This can be annoying as that means users have to fix parameters one by one, rather than getting a whole list and being able to do it en-masse. We should fix this system by potentially collecting parameters before throwing an error.

Similarly it might be useful for this parameter error to point to where in the code this check is happening, so that more advanced users can investigate the exact assertion statement that is breaking the code, for debugging or development purposes.