Optionally exit with zero code, event if limit broken.

In some cases, when you want to monitor size changes and limit in a non-blocking way it's nice to have the opportunity to generate JSON with the result (to show in a merge request, for example), that shows that limit is broken but don't exit with non-zero code to not stop the pipelines.