resolve package is breaking after 1.11.0 change, don't update it for now

[danwbyrne]

Description

Not sure what they changed, but the overall calling order of resolve to our mock filesystem in tests is very broken. When compared to how it operated (side-by-side with another version running) they touched different mock filesystem methods completely. Ignoring for now as it isn't pressing that we update it anyway.

Steps to Reproduce

1. update to resolve 1.11.1 in @neo-one/editor
2. tests fail

see: browserify/resolve#192

edit: this is actually coming up when cascading to other packages like webpack, putting it in the resolutions package field for now.