Do not limit nesting depth of parsed JSON

[wfleming]

I turned up some instances of files that killed the engine due to
deeply nested JSON results from the parser: the JSON gem by default puts
a limit on this.

👀 @codeclimate/review

[brynary]

Historical context: In the past we've parsed with unlimited depth. Since this is in an engine, I think it might be worth doing that as the simplest possible thing (and not adding more exception handling, which can be troublesome) and seeing where that leaves us.

[wfleming]

@brynary OK, I didn't realize we had an unlimited depth in classic analyzer. Will update.

[gdiggs]

LGTM

[pbrisbin]

I think this can be private. Ruby's method access is an odd-ball:

• private - cannot be called with a target (even self. will raise)

• protected - can only be called with a target if you're the same class or a subclass

  This is mostly (only?) useful for otherwise private attributes that need to be invoked with a target as part of an equality check:

  class Foo
    def ==(other)
      private_thing == other.private_thing
    end
  end

  This won't work if #private_thing is actually private, so it would be protected.

[wfleming]

I think I do this habitually more for how it reads than how it actually works. But good point, changing.

[pbrisbin]

One nit. LGTM