Improving command help content

[leggetter]

We should take some time to make sure that the help messages for each command don't make too many assumptions about in-depth BRJS knowledge.

For example, the dep-insight command talks about 'source modules'. Is there a simpler way of explaining this without the need to introduce a new concept?

Related to #548 and #549.

2.0.0-p353 in sdk/
› ./brjs help dep-insight
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128M; support was removed in 8.0
creating plugins
performing node discovery
making plugins available via model
BladeRunnerJS version: v0.7-108-g0b13594, built: 28 April 2014 22:18 BST

Description:
  Show inverse dependencies for a given source module.

Usage:
  brjs dep-insight <app-name> <require-path> [<aspect-name>] [-p|--prefix] [-a|--alias] [-A|--all]

Help:
    <app-name>
        the application to show dependencies for

  <require-path>
        the source module to show dependencies for

  [<aspect-name>]
        the aspect to show dependencies for (default: default)

  [-p|--prefix]
        display dependencies for all source modules starting with the given
        require path

  [-a|--alias]
        display dependencies for an alias rather than a require path

  [-A|--all]
        show all ocurrences of a dependency

create-library command should provide all the "type" parameter options within the help text

./brjs help create-library

› ./brjs help create-library
Description:
  Create a new empty library within a given application.

Usage:
  brjs create-library <target-app-name> <new-library-name> [(-t|--type) <type>]

Help:
    <target-app-name>
        the application the new library will be created within

  <new-library-name>
        the name of the library that will be created

  [(-t|--type) <type>]
        (default: br)

The default value for --type is br. What are the other options?

The other option is thirdparty as per the docs: http://bladerunnerjs.org/docs/use/use_libraries/#tocAnchor-1-3