Implement a mandatory password reset for all editors

See http://blog.musicbrainz.org/?p=1844 for why we need this.

Checks the `last_login_date` for editors on login, and if that's before
`$LATEST_SECURITY_VULNERABILITY` they are immediately logged out and forwarded
to the "change password". This page has been updated to work when people are
logged out, requiring they enter a username. The username is prefilled from the
currently logged in user's name, or can be filled in from query parameters. The
login form uses this to fill it in for a better user experience.
Make sure that cookie logins are subject to security vulnerability checks
Add a message as to why user's need to change their password
Rename setup_test_db_for_selenium.pl → script/setup_development_db.pl.

Now that selenium tests have been removed, a script to set up a
database for selenium is no longer needed.  However, the script is
still useful as a general way to set up a minimal database.  I changed
it to operate on the production/development database instead of a test
database.
Add SQL update scripts which deduplicate tracklists.

This changes made by these scripts are:
  1. replace tracklist column in tracks with a medium column
  2. make copies of each track so a track is not re-used on multiple media
  3. add gid column to the track table and generate uuids for each track
  4. add track_gid_redirect table
Update reduplicate tracklist sql changes + test data dump script.

- Also update tracks attached to a single tracklist in 20130220-reduplicate-tracklists.pl
- Also replace the track insert/delete triggers in 20130220-update-track-trigger.sql
- Output tracks in script/release-group-sql-dump.pl, and dump link tables in the correct order.
- Include some temporary scripts (resetdb.sh, cleandb.sh) useful during development of this branch.
MBS-1839, Include work types in webservice test data dump.
MBS-1839, more track identifier database changes in the form of update scripts.

- Re-introduce track_count column (on medium, previously on tracklist).
- Update triggers to keep track of the track_count.
- Initialize medium.track_count with correct values (20130305-update-medium-track-count.sql)
- Remove search_path wrangling from script/release-group-sql-dump.pl
- Initialize medium.track_count with correct values (script/release-group-sql-dump.pl)
MBS-1839, Replace t/sql/webservice.sql with a new dump from the new schema layout.
MBS-1839, Implement database changes from sql/updates/* in admin/sql/Create* and Drop*
MBS-1839, remove duplicate b_upd_medium trigger and remove tracklist from SetSequences.sql
MBS-1839, include updated webservice.sql generated from mbs-1839-schema-changes-as-updates branch.
MBS-1839, Add track_gid_redirect table.
MBS-1839, updated generated admin/sql/* files by running admin/GenerateSQLScripts.pl
MBS-1839, Swap out the tracklist column for a medium column in the tracklist_index table, and then rename it to medium_index.
MBS-1839, update resetdb.sh to use the correct sql/updates/* scripts and add missing ; in 20130220-reduplicate-tracklists-part2.sql.
MBS-1839, renamed script/setup_development_db.pl -> script/setup_development_db.sh
MBS-1839, Don't confuse TEST and READWRITE databases in db setup scripts.
MBS-1839, Slightly simplify track duplication query and don't touch the track id sequence.
MBS-1839, Fix track gid generation to result in the same uuids on replicated servers.