Created new files for browser
Browser platform is now being created from cli
Remove references to "firefoxos"
CB-7190: Add browserify support in cordova-lib/cordova-cli
CB-7228: Cordova prepare --browserify runs on all installed plugins
CB-7001: Create a --browserify option for run action
CB-7140 Check plugin versions in local search path

`cordova plugin add id@versionspec`
`cordova plugin add org.apache.cordova.file@>=1.2.0`

Plugins from local search path with the given id but with a version that does
not satisfy versionspec will be ignored. If several satisfying plugins are
found, the one with the highest version will be used.
CB-7091: Remove check_requirements() funcs from platform parsers

No longer used, removing. They were either:
1) Empty
2) Duplicating the chqck_reqs call that is also done by platform create scripts
3) In Ubuntu duplicated the code from check_reqs
CB-7091: Remove check_requirements() funcs from platform parsers

No longer used, removing. They were either:
1) Empty
2) Duplicating the chqck_reqs call that is also done by platform create scripts
3) In Ubuntu duplicated the code from check_reqs
CB-7100: Use npm based lazy-load by default

fixing test to use imaginary version to avoid colliding with actual local content
CB-7234 added better outputs for plugin registry workflows
CB-7228: Fixed issue with "cordova prepare --browserify"
CB-7260 Get cordova-android 3.5.1 instead of 3.5.0
Add JSCS config file

But not running it as part of `npm test` yet.

See discussion here:
http://markmail.org/thread/rzzvn2ax3tqzabfw

JSHint people want to focus on syntax linting and are dropping style oriented
options. They recommends using JSCS (in addition to JSHint) for style:
https://github.com/jshint/jshint/issues/1339

JSCS has recently added the options dropped from JSHint.
https://github.com/mdevils/node-jscs/issues/102

This commit contains a JSCS config file with some basic settings that generate
very few errors with the existing cordova-cli and lib code.

My goal is to eventually run JSCS together with JSHint as part of `npm test`.
The nice thing about JSCS is that style flame wars can be way more structured
with it as we can argue about very specific well named JSCS config options :)

I'm using it with SublimeLinter-jscs
https://sublime.wbond.net/packages/SublimeLinter-jscs
Style fixes - white space only
Allow plugin modules to be .json files
CB-7255 Fixed writing plist unescaped

- Use current plist npm instead of plist-with-patches
- Solve resulting deprecation warnings

We originally switched to plist-with-patches to add some patches which didn't
get through to the upstream plist at the time. The upstream plist has those
fixes now, and some more.

github: close #70
Add link to BuildBot at ci.cordova.io in README
Fix error in comments for munge functions
Style fixes - comments

//xyz -> // Xyz (space and capitalization).