Establish a base for linking in NPM sources to be exposed

* Sort package.json packages
* Use absolute versions for npm packages... closes #321
* Change README.md to reflect moved/new packages
* Fix whitespace `function(` to `function (` from #331
* Using for express-minify for server side .js and .css minification ... applies to #330
* Create `./routesStatic.js` and move/create all static routes into it ... applies to #330
* Remove static copies which closes #330

Parallel change e.g. no new dependency updates such as *font-awesome* and *bootstrap*

Many thanks to @jerone, @Zren, and @cletusc for assistance in team biz for these issues.
I am trying to clean up `app.js`.

Again, `routes.js` is where ALL route handlers are defined. That includes MVC controllers. That includes error pages. That includes static files. We could make a `routesControllers.js` (origionally what I considered `routesDynamic.js` but that name isn't very good), however it would be imported inside of `routes.js`, not `app.js`, because that's where routes are defined.

The hierarchy would be:

* `app.js`
  * `routes.js`
    * `routesControllers.js`
    * `routesStatic.js`
    * 404 error handler

I named it routesStatic/routesControllers because it keeps the files together when looking in the folder. We could use underscores, but it wouldn't be consistent with the rest of our filenames. We could have a routes subdirectory, but then we'd have to pass in the root `__dirname` everywhere and it would suck, I've tried it before (as `app.__dirname`).