Closes #6939 

* Resolve Next.js loaders first

Next.js loaders should be resolved first, then node_modules. There is no need for NEXT_PROJECT_ROOT_NODE_MODULES anymore since all our loaders are internal

* Move wasm to end of array

Since wasm isn’t the main target for Next.js it makes no sense to try and resolve it as the first value, as it would incur a file not found for nearly all files in the compilation

Checking the stats first. But at least until https://github.com/zeit/next.js/issues/6950 is figured out we should disable it for serverless builds as it's also disabled for zeit.co serverless builds.

By using `var` we opt-out of the LibraryTemplatePlugin. Considering we have our own loader for registering pages this makes sense.

* Add babel-plugin-transform-async-to-promises

* Remove unit test as this is covered by integration tests

* Add lambda version of shared chunks

* Fix test on Windows

* Make chunk graph more accurate

* Include shared files in every page

Previously this didn't work properly with nested pages.

* Add a build all but specified pages mode

* Always include reserved pages in build

* Add tests for ignore pages

* Output a more correct message for debug builds

* Adjust wording

* Fix nested position

* Drop front commit

* Emit new page chunks key with all involved files for a page

* Add useRequest hook and RequestContext

* Add useRequest hook and RequestContext

* Fix merge conflict duplicate import

This adds a query for debugging AMP bind init data

To prevent slowing down we only handle on catch

This reverts commit 5dc9f55e.

* Temporarily only do one pass

* Add types

* Add ** page globbing support

* Update check

* Compute hashes of files during emit

* Fix tests

* Remove test from old location

* Correct the target