Tighten findAllApplicationScripts heuristics

When the directory does not contain package.json, limit the traversal
to top level javascript files and well-known subdirectories:
    lib/
    node_modules/
    test/

This should prevent unintentionaly broad searches like
all files in C:\ drive.
Ignore EACCESS errors when listing sources
Cache results of ScriptFileStorage.listScripts.
Speed up initial parsing of source-map URLs

`ScriptManager._getSourceMapUrl` accepts an optional parameter
`scriptSource`.

`DebuggerAgent._reloadScript` asks V8 to include script sources
in the response.

This way it's not necessary to send another request for each script
that is loaded by V8 at the time when Node Inspector is attaching to
the process.
bin/inspector: Add -h -v --version options

Refactor lib/config and bin/inspector, split printHelpAndExit into
two parts. The first part is building the help message and stays in
lib/config as `config._describeOptions`. The second part (print and
exit) is moved to bin/inspector.
Clean up node-debug help message

- Reword so lines are closer to 80 chars wide (yargs does not wrap
  option descriptions).
- Use basename of $0 as command name, so full path
  (/usr/local/bin/node-debug) isn't printed in the usage.
Update .npmignore

Add
  .travis.yml
  MAINTAINERS.md
Lower the frequency of auto reloads

Change the timeout used to reload the front-end page when the debugged
process is not connected. Old value: 100ms, new value: 400ms.
Defer "scriptParsed" until "Page.getResourceTree"

DevTools front-end expects to receive Page.getResourceTree response
before any "scriptParsed" events. When "scriptParsed" arrives first,
the source-map handler throws an exception.

Add FrontendClient methods pauseEvents() and resumeEvents().

Change PageAgent to EventEmitter, add a "resource-tree" event that
is emitted at the time when the Page.getResourceTree response is sent.

FrontendCommandHandler uses these two features to pause events on start
and resume them on "resource-tree".
Update AUTHORS
Rename readme.md to README.md

Use the most common variant.
README restructuralization

Move the sections around, put a Quick Start via `node-debug` on the top.

Clean up the content, update links.