Adding nesh-doc plugin as a default plugin, automatically enabled

Shows some documentation for an expression; invoke it by typing Ctrl-Q
inline after an expression

Ex.
```
    nesh> process.on<Ctrl-Q>
    [Function] (type, listener)
```

Hit Ctrl-Q twice to see more information, ex. the entire source code in the
case of a function.

Ex.
```
    nesh> process.on
    [Function] (type, listener)
    function (type, listener) {
          if (isSignal(type) &&
              !signalWraps.hasOwnProperty(type)) {
            var Signal = process.binding('signal_wrap').Signal;
            var wrap = new Signal();
    ...
```

You can also invoke it with the `.doc` keyword.

Ex.
```
    nesh> .doc process.on
    [Function] (type, listener)
```

This works for all objects, but is most useful for functions and sometimes
classes. I'm planning to write up a document about how to annotate your
code in a way that the doc module can understand if you want to make your
source more readable that way, but doing that isn't required for this
plugin to be useful. The most useful thing is usually just quick access to
what parameters a function expects.
Merge pull request #13 from ccheever/nesh-doc

Adding nesh-doc plugin as a default plugin, automatically enabled. Fixes #13.
Document REPL commands
Version bump to 1.5.0
website.mb spelling: Asyncronous -> Asynchronous
Merge pull request #14 from ccheever/patch-1

website.mb spelling: Asyncronous -> Asynchronous. Fixes #14.
Adding nesh-doc plugin as a default plugin, automatically enabled

Shows some documentation for an expression; invoke it by typing Ctrl-Q
inline after an expression

Ex.
```
    nesh> process.on<Ctrl-Q>
    [Function] (type, listener)
```

Hit Ctrl-Q twice to see more information, ex. the entire source code in the
case of a function.

Ex.
```
    nesh> process.on
    [Function] (type, listener)
    function (type, listener) {
          if (isSignal(type) &&
              !signalWraps.hasOwnProperty(type)) {
            var Signal = process.binding('signal_wrap').Signal;
            var wrap = new Signal();
    ...
```

You can also invoke it with the `.doc` keyword.

Ex.
```
    nesh> .doc process.on
    [Function] (type, listener)
```

This works for all objects, but is most useful for functions and sometimes
classes. I'm planning to write up a document about how to annotate your
code in a way that the doc module can understand if you want to make your
source more readable that way, but doing that isn't required for this
plugin to be useful. The most useful thing is usually just quick access to
what parameters a function expects.
Document REPL commands
Version bump to 1.5.0
website.mb spelling: Asyncronous -> Asynchronous
Merge remote-tracking branch 'upstream/master'