Converting the app to Sails 0.10

Followed the recommendations given in
http://sailsjs.org/#/documentation/concepts/Upgrading to
convert the application to Sails .10. The changes are listed
below:

* Changed done to exec when executing a query in Waterline.
* Added findOne endpoints to policies file and to the controllers.
* Replacing the 404/500 responses with the responses directory.
* Add bootstrap code to load our services
* Update tests that expect a 201 to expect a 200, at least until
  the bug in Sails is fixed
* Removed adapters.js configuration file, moving the connections
  data to the local.js
* Removed customMiddleware from config/auth.js, and moved content
  to the new config/http.js
* Renamed export from config/controllers from controllers to blueprints
* Added config/globals.js, config/models.js

Fixes #217
Removing reliance on Sails-provided async.

Sails provides the async module automatically. This doesn't work
for us because we have custom bootstrap that needs to use async
before Sails is completely available.
Adding sails-build-dictionary to the package file.
Updating the INSTALL document to refer to the new sails-postgres fork.

We've created a fork of sails-postgresql in 18F to contain the
soft delete changes. The INSTALL document was updated to refer
to this fork instead of the Innovation Toolkit fork.
Adding a limiter to the grunt watch to work around limits.
Adding a note for troubleshooting the EMFILE issue to the INSTALL doc.
Added a note about migrate mode support.
Merge pull request #454 from DavidEBest/devel-sailsupgrade

Converting the app to Sails 0.10