reported to v8 in http://codereview.chromium.org/6056006/

This path adds an additional cache to the module system for caching the
location of previously required modules. Since it is embedded in the
loop that iterates over all require.paths, this patch also handles the
case where require.paths is being modified.

The patch also cleans up some code around it.

See: https://groups.google.com/forum/#!topic/nodejs-dev/QGGlrvLDHVs

See: https://github.com/ry/node/commit/2e5dfafcb06f769889bd4d08a07d1c53346e7be7#commitcomment-239719

require is caching the compiled code but still stating the filenames.
https://groups.google.com/d/topic/nodejs-dev/QGGlrvLDHVs/discussion

This reverts commit 9e31e083.

Use process.platform == 'win32'

Just put a file lib/_third_party_main.js into the build directory and take
it from there.

TODO:

debug> run script.js

The previous cleanup patch broke module loading in the the REPL by
not initializing require.paths.

Change to end() behavior in 33c339 was breaking it. end() should wait for
connection before dumping. Changed test-net-connect-timeout to use destroy()
instead.

Also make socket.end() destroy connection if still trying to connect.
Previously was ignoring.

Fixes sporadic test-next-tick-ordering.js failures

Avoids race. openssl s_server is a terrible program.

Conflicts:
	deps/libeio/config.h.in