Add support for updating languages. Closes #187.

Languages can now be added and removed inline thanks to the awesome
Select2 library. The list of accepted languages can be customized in
settings.yml.

Demo:
![Editing languages in Ohana API
Admin](http://cl.ly/image/46132V282d1o/Screen%20Recording%202014-09-11%2
0at%2004.20%20PM.gif)
Merge pull request #231 from codeforamerica/187-admin-languages

Add support for updating languages. Closes #187.
Use Select2 for service areas field.

Since the list of valid service areas is defined in settings.yml, it
should be used to populate the choices in the select field in the admin
interface. That way, it won’t be possible to submit an invalid value,
and users won’t have to guess what to enter.
Merge pull request #233 from codeforamerica/select2-for-service-areas

Use Select2 for service areas field.
Use Select2 to update service keywords inline.

Instead of cluttering the interface with a bunch of keyword fields laid
out vertically, and with each having a “delete this keyword” button, we
can use Select2 to add and remove keywords inside a single input field.
Merge pull request #234 from codeforamerica/use-select2-tags-for-service-keywords

Use Select2 to update service keywords inline.
Slow down load_data rake task to prevent errors.

Recently, running the load_data rake task has been triggering the
`Geocoder::OverQueryLimitError`. My guess is that perhaps Google has
lowered their requests per second threshold. Adding a sleep of 0.2
seems to do the trick.

I also added a note about the ability to use a different geocoding
service if desired, as explained in the Wiki.
Make tld_length setting a config var.

This makes it easier to adjust the setting since it doesn’t require
committing and pushing code to make a change.
Update geocoder to version 1.2.5
Update Rails to version 4.1.6
Update taxonomy to Open Eligibility 2.0

I only updated the structure and the names of the categories. Although
OE 2.0 uses new IDs, I kept the same IDs as before because it makes it
easier to upgrade if you already assigned categories to services, and I
prefer the hierarchical ID system from version 1.0.

Closes #124.
Update Figaro to version 1.0.0

Now that 1.0.0 fixes the issue with setting heroku config vars, I’ve
updated application.example.yml to allow using different variables
based on the environment.

I also updated the setup_heroku script to use the figaro command to set
the customizable config vars.
localise settings yml
localised address model and tables to be uk friendly
dev and test usernames and pass for local development