V0.6

Rewrite of freedom build system.

## High Level Changes:
* Classes now ```require()``` as needed, browserify used for build process
* No Global state remaining
* Entry rewritten without the weird previous packaging
* Bundling of core providers changed to be in the new entry system
* Custom APIs available outside of freedom
* Unified API between event and API interface
* Fixes #95 , #93 
Also a related question, in freedom-social-xmpp, both main.js and ux.js use a freedom object, even though they are in different contexts (main.js is in the "top level module", while ux.js is the privileged environment with the DOM and it uses window.freedom).  In freedom 0.6, does one or both of these have to become freedom()?

Also in the freedom-social-xmpp case it seems like main.js is both a producer and consumer.  It "produces" (emits events that are picked up by ux.js), but also is a "consumer" of the social provider API....so that further confuses how we want to use freedom()