Switch to using bower to manage static dependencies

This PR removes all of the static libraries from our repo and instead uses bower to manage them. It requires that nodejs, npm and bower be installed on your machine. There is a new paver setup_static command which will fetch the dependencies and store them in geonode/static/.components and then invoke bower-install to put just what we need into geonode/static/lib .. The paver package command is now setup to ignore whats in geonode/static/.components, so only what makes its way into geonode/static/lib will be included in our packages.

I've carefully tried to update all the paths to match this new setup. We may find a few more places where they need to be updated. Once this is pulled, we can all test locally and on the dev server.

NOTE: There is one small bug with this setup still. The permissions form in the upload is not quite working right after the shuffle. @simod do you think you might be able to take a look at this?