just let multijson handle choosing the JSON parser

ridley has a requirement, chef has a requirement; it's like everyone has an opinion
so let's just have multijson take care of it for us.
disable class initialization when parsing json with a json_class field/value
update lockfile spec to check for existence of file
ignore whitespace and other annoyances when checking JSON in features
update features will compare JSON and not exact text
lock to chef <= 11.0.1 to prevent json dep conflict with vagrant
version bump 1.1.4
Merge pull request #339 from RiotGames/json-sanity

JSON (in)sanity
Merge branch '1-1-stable'

Conflicts:
	berkshelf.gemspec