Rename long-description to long_description

If we don't do this, it's a pain to get it back out when importing.
Rename hook args to arguments for consistency
Mark parser util as executable by PHP
Output the JSON to stdout

Rather than handle it ourselves, use standard terminal output redirection.
Split CLI functions into a separate file
Ignore wp-content
Ensure we always use forward slashes for paths
Simply docblock handling
Actually commit the plugin part

I'm an idiot.
Ignore composer folders
Don't block parsing files inside the wp-content folder

Currently, WP Parser is meant to be run in the root directory of a
WordPress site to generate documentation for WordPress core, and
therefore ignoring everything in wp-content makes sense. However, this
makes it harder to generate the JSON in a specific directory -- say for
a specific plugin.

One solution is to require people to check out a copy of that plugin
outside a wp-content folder, and run the documentation there. However,
as WP Parser is hopefully going to be used by all great plugins, this
puts a speedbump in the way of the plugin authors.

The onus should be on the person running WP Parser to decide which
directories/files need to be looked at, rather than blocking all
wp-content paths.
Update parser to support scanning an individual file, as well as a directory.
Merge pull request #3 from paulgibbs/b5

Don't block parsing files inside the wp-content folder
Merge pull request #7 from paulgibbs/b6

Update parser to support scanning an individual file, as well as a directory.
Merge pull request #2 from paulgibbs/b1

Add .gitignore for composer files
Merge pull request #8 from rmccue/exportimport

Add importing & exporting to the parser