debugger: don't set the `repl.prompt` string

It wasn't doing anything, and actually due to
3ae0b17c76f693dd2e68a46f78c7dc7f595b33c6, it was causing
the readline `prompt()` function to be overwritten
which throws an error in the REPL shortly after.
src: remove `node_isolate` from source

fix #6899
node_internals: add missing env-inl.h include
async-wrap: include additional ProviderType

NONE has been moved to 0.

CONNECTWRAP has been removed and instead the incoming connection
provider type is passed.

FSREQWRAP has been included.

{Req,Write}Wrap have been split up and now pass the callers provider
type, since the class defines what is going on not who is calling it. So
now the "provider" constructor parameter is now required on both.

CARES has been moved to QUERYWRAP.

AsyncWrap::provider_type() now returns ProviderType.
tracing: WIP pass provider filter to AsyncListener
tracing: properly check asyncQueue length

The asyncQueue length was not properly checked when running the create
callbacks. Leading to no callbacks being run.
doc: update AsyncListener usage

There were a few errors in the functionality that users could expect
from AsyncListener.
tracing: pass context to AsyncListener error() cb

The context passed to the error() callback is that of the originating
function call in the call stack. Not the context of the function that
actually threw.
tracing: pass call callbacks on correct provider

This will make it so callbacks are only called on the correct provider,
but still reserve the async stack.

Also the provider type (e.g. TCP) will be passed as the second argument
to the create() callback.

process.nextTick() is a special case. Because of its implicit call style
within core code the callbacks will always be called for all nextTick().
doc: additions explaining new AL functionality
WIP