Bump up selenium version

Needed to stay in sync with Firefox. This is going to be required
periodically until we switch to using an non-auto-updating version of
firefox, like iceweasel.
Simplify login code
Add plugin function to run setup code for all UI tests
Merge pull request #1465 from RickMohr/ui-tests-clear-caches

Ui tests clear caches
Fixes #1463 - Text issues with registration/validation
Return date format in API instance info
Fixes OpenTreeMap/otm2-addons#133
Merge pull request #1466 from maurizi/api/date-format

Return date format in API instance info
Fixes #1422, Fixes OpenTreeMap/otm2-addons#131
Fixes #1470
Fixes #1427
Fix user photo upload.

The endpoint was not being passed properly to the included template

Fixes #1468
Merge pull request #1474 from maurizi/fix/1468/user-photo-upload

Fix user photo upload.
Merge pull request #1473 from mtedeschi/fix/1463/change-account-text

Release changes, plus other Bootstrap fixes
Pass region code, not region object (and rename variable)

Not sure how this ever worked, or why changing to Django 1.6 would have affected it.

Lower down this gets converted to a string using `str(...)`, and apparently that call used to extract the `ITreeRegion.code` field. But I see no method on `ITreeRegion` that would have accomplished that.

Fixes #1472

rename
Merge pull request #1475 from RickMohr/fix-eco

Pass region code, not region object
Change password reset API endpoint

This endpoint has been broken since the creation of the API. Nesting the
password reset under users/{user-id} is not possible. If the user is
resorting to sending a password reset email, then they cannot log in and
the app cannot know their user ID.

This is a major change to an endpoint, however this cannot break any
clients, since no clients have ever hit this endpoint successfully. For
that reason, I am _not_ bumping the API version up from 3 to 4.
Merge pull request #1479 from jwalgran/topic/fix-password-reset-api-endpoint

Change password reset API endpoint
Update password reset request API

My first crack at fixing this did not work. The passing unit test did
not reflect the runtime behavior, which was a 403 CSRF-relates error.

I rewrote the test to make sure it passed through the entire web stack,
and then refactored the endpoint using the nested function style,
incorporating signature checking and CSRF-exemption. I also added a
check to see if the email was associated with an account and return a
failure message if not. This prevents clients from showing a "check your
email" message when the server did not even attempt to send an email.
Merge pull request #1481 from jwalgran/topic/really-fix-pass-reset-api

Update password reset request API