test: delete invalid http test

The test is no longer valid for the original scenario.

It now fails intermittently because of two other issues:
1. Since the client is only processing one readable event, the
   client request is not enough to keep the process alive and the
   process can exit before the desired events have been raised.
2. Reading just 1 byte is not enough to guarantee that the parser
   will eventually consume all the data and raise the desired
   parse error. I tried postponing the server.close() to address
   the issue at [1], but then the test just hangs sometimes.
zlib: add sync versions for convenience methods
debugger: remove unused definition `currentSource`

Client's property `currentSource` has no use throughout the project.
node: make AsyncListenerInst field more explicit

"flags" could mean one of many things, and multiple flag types could be
checked. So make the field more explicit on what type of flags are being
stored.
async_wrap: initialize at end of constructor call

Don't initialize AsyncWrap until after the parent constructor has
completed. This should allow us to safely pass the creation context to
the "create" callback.
node: pass calling context to create/error

Now that the instance has finished instantiating before create is
called, it is possible to pass the calling context as the first
argument.

The current calling context is stored within scope to access the
asyncQueue attached. This has the added benefit of allowing the context
to be passed to the error callback.

Currently this change will cause a SEGFAULT if properties are inspected
from specific contexts!!!