events: Make the EventEmitter class monomorphic

Always add domain, _events, and _maxListeners properties, set to the
default values at first.

Leads to a very very slight perf improvement when using setMaxListeners,
or dealing with a lot of EE objects that don't have any listeners.
npm: Upgrade to 1.1.65
V8 build: 'echo -n' considered harmful
2012.10.25, Version 0.8.13 (Stable)

* V8: Upgrade to 3.11.10.25

* npm: Upgrade to 1.1.65

* url: parse hostnames that start with - or _ (Ben Noordhuis)

* repl: Fix Windows 8 terminal issue (Bert Belder)

* typed arrays: use signed char for signed int8s (Aaron Jacobs)

* crypto: fix bugs in DiffieHellman (Ben Noordhuis)

* configure: turn on VFPv3 on ARMv7 (Ben Noordhuis)

* Re-enable OpenSSL UI for entering passphrases via tty (Ben Noordhuis)

* repl: ensure each REPL instance gets its own "context" (Nathan Rajlich)
Merge branch 'v0.8.13-release' into v0.8
Now working on 0.8.14
blog: Post for v0.8.13
events: Don't clobber pre-existing _events obj in EE ctor
2012.10.25, Version 0.8.14 (Stable)

* events: Don't clobber pre-existing _events obj in EE ctor (isaacs)
Merge branch 'v0.8.14-release' into v0.8
Now working on 0.8.15
blog: Post for v0.8.14
blog: Correct shasums for v0.8.14
windows: correct outputs list in "node_etw" gyp target

The gyp target node_etw didn't list its output dependencies. This
was causing virgin builds to fail with a "failed to open file for
write" error.

With this corrected outputs list, gyp reliably pre-creates
required output directories.
Print warning when maxTickDepth is reached
doc: reflect hostname v. host preference in examples

The documentation for http.request and https.request states that
`hostname` is preferred over `host` so the code examples should
use that option name.
doc: remove duplicate set of options
zlib: reduce memory consumption, release early

In zlibBuffer(), don't wait for the garbage collector to reclaim the zlib memory
but release it manually. Reduces memory consumption by a factor of 10 or more
with some workloads.

Test case:

  function f() {
    require('zlib').deflate('xxx', g);
  }
  function g() {
    setTimeout(f, 5);
  }
  f();

Observe RSS memory usage with and without this commit. After 10,000 iterations,
RSS stabilizes at ~35 MB with this commit. Without, RSS is over 300 MB and keeps
growing.

Cause: whenever the JS object heap hits the high-water mark, the V8 GC sweeps
it clean, then tries to grow it in order to avoid more sweeps in the near
future. Rule of thumb: the bigger the JS heap, the lazier the GC can be.

A side effect of a bigger heap is that objects now live longer. This is harmless
in general but it affects zlib context objects because those are tied to large
buffers that live outside the JS heap, on the order of 16K per context object.

Ergo, don't wait for the GC to reclaim the memory - it may take a long time.

Fixes #4172.
zlib: pass object size hint to V8

Inform V8 that the zlib context object is tied to a large off-heap buffer.

This makes the GC run more often (in theory) and improves the accuracy of
--trace_external_memory.
tls: delete useless removeListener call

onclose was never attached to 'end' so this call to remove this listener
is useless.  Delete it.