report issues found while running overlap_collector back to user

[smason]

if the operation failed, we should be reporting warnings and errors back as these probably indicate an issue with the input geometry that could turn out to be useful to the user

Helen's step file using broken sectioning code causes some internal errors to get set, which might be nice for testing!

[smason]

might be nice to report warnings even in the case of success, maybe at debug level as they don't seem to have much effect

[smason]

Colin's data file M31202352_A.stp has errors, need to run with --no-check-geometry

Might want to add a flag that still checks, but doesn't fail on errors

or maybe use exit codes better so we can differentiate between these cases