Feature: Raise step error on n task error count

[evamaxfield]

Use Case

Please provide a use case to help us understand your request in context
Related to #55, with the introduction of the errors.json file, the underlying reason for that issue and this one is that in the case where 10000 tasks are being run in a single task and only few error, we don't want to error the entire downstream pipeline. This would allow us to set some integer limit on raising an overall step error on the tail end of run.

Solution

Please describe your ideal solution
Add a post run check to the log_run_params wrapper function that compares the length of the errors.json file if present to the integer value set.

Alternatives

Please describe any alternatives you've considered, even if you've dismissed them