Preview report can't process a catalog_preview that has debugging enabled

[hpcprofessional]

catalog_preview has a --debug option

If this option is used, it populates the output with data such as:

^[[0;36mDebug: Evicting cache entry for environment 'development'^[[0m
^[[0;36mDebug: Caching environment 'development' (ttl = 0 sec)^[[0m
^[[0;36mDebug: Evicting cache entry for environment 'development'^[[0m
^[[0;36mDebug: Caching environment 'development' (ttl = 0 sec)^[[0m
^[[0;36mDebug: Evicting cache entry for environment 'development'^[[0m
^[[0;36mDebug: Caching environment 'development' (ttl = 0 sec)^[[0m
^[[0;36mDebug: Evicting cache entry for environment 'development'^[[0m
^[[0;36mDebug: Caching environment 'development' (ttl = 0 sec)^[[0m
^[[0;36mDebug: Using settings: adding file resource 'confdir': 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'^[[0m

(note the ASCII color codes)

This is also reproducible if one has perfectly valid json output but puts a comment at the top line:

#No comments in JSON!
{
  "stats": {
...

Anyway, it would be a nice bonus feature if the script could ignore stuff until it encountered JSON, at which point it would start to process the json and then explode if it had any subsequent parse errors.

Alternately, it could just error out and say "$file is not valid JSON."

Dealer's choice. (Right now it explodes with a stack trace)