Fix the resolve options for a browser target

[homer0]

What does this PR do?

I added two extra settings for the resolve plugin:

• browser: Set to true when the target is for browser. Allows the plugin to correctly resolve packages that use the browser key. Like Jimple.
• preferBuiltins: Set to true when the target is for Node. It shouldn't try to use native Node modules when the target is for browser.

How should it be tested manually?

For browser, you can try building a browser target that imports Jimple.

For preferBuiltins, you can try building a browser target that imports querystring.

And of course...

npm test
# or
yarn test

[coveralls]

Pull Request Test Coverage Report for Build 8

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 4:	0.0%
Covered Lines:	1273
Relevant Lines:	1273

---

💛 - Coveralls