Fix the state of the dashboard after refreshing.

The dashboard state was broken after its first load. The columns were no
longer interactive, nor was the Edit Column icon. The relative timestamp
columns showed absolute times.

We now set up the state again once we've completed a load.

Fixes bugs #2993 and #2994.
Merge branch 'release-1.7.x'
Fix an XSS vulnerability in the reviews dropdown.

The reviews dropdown had a bad vulnerability where it would assume the
user's full name is valid HTML. This allowed the user to craft a script
tag that would be executed every time the name appeared in the dropdown.

This vulnerability exists in 1.6.x, 1.7.x, and the in-development 1.8.
There are no known attacks in the wild.

This was reported by Craig Young at Tripwire.
Increase the max size of the timezone field.

The timezone field's max size was too small for the longest timezone
(America/Argentina/Buenos_Aires). The max size is now set to 30 to allow
for this.

Fixes bug #3005.
Reviewed at http://reviews.reviewboard.org/r/4230/
Fix an XSS vulnerability in the reviews dropdown.

The reviews dropdown had a bad vulnerability where it would assume the
user's full name is valid HTML. This allowed the user to craft a script
tag that would be executed every time the name appeared in the dropdown.

This vulnerability exists in 1.6.x, 1.7.x, and the in-development 1.8.
There are no known attacks in the wild.

This was reported by Craig Young at Tripwire.
Release Review Board 1.6.17.
Merge branch 'release-1.6.x' into release-1.7.x
Release Review Board 1.7.10.
Merge branch 'release-1.7.x'
Update the docs database for the latest schema changes.
Log useful output when the docs generation fails to find DB entries.
Fix unwanted saves when setting/getting ReviewRequest.commit.

ReviewRequest.commit behaved unlike any other attribute of a model.
Getting or setting it would trigger a save of the model.

This caused two problems.

First, we could end up loading a ReviewRequest and getting the commit,
triggering a save too early, and messing up state. The webapi docs
generation was impacted by this, and it led to failures.

Second, call sites that updated the commit and other properties resulted
in two database hits.

We no longer automatically save when setting. We still do migrate the
changenum to commit_id when getting, if needed, but we do it as an
atomic change in the database and not a full model save.
Remove a debug statement.
Fix the docs database to not have missing data.

The recent update to the docs database was broken due to the commit_id
early-saving problem. This restores from a previous commit and updates
for the commit_id schema.