(Bug 4784) Use default value only if we haven't POSTed yet

Also explain what the default is meant for, to distinguish it from other
ways of setting the visible form field value
(Bug 3994) : New "deleted account" page

* Shows an initial paragraph according to your relationship with the
   account and whether it is a community

* Shows the reason for deletion if there is one

* Shows the bit about being notified upon purge if you are logged in and
   are not the owner/admin.
(Bug 3994) : Don't offer to track protected usernames.
(Bug 3994) : Now show "relationship text" & link.

If the user has granted access to or subscribes to or is a member of
the deleted account, tell them this and offer a link to change that.
(Bug 3994) : Tidied up indents, removed trailing spaces
(Bug 3994) : Changes as requested in code review

* Cleanup of spaces & linebreaks

* Changed $dbr to $dbcr

* Only look up the deleter in the db when it's a community

* Tweak to page formatting
(Bug 3994) : Changed interpolated variables to bound params in db query
(Bug 3994) : Corrected SecurityAttributeChanged.pm for best practice as per pull request comments

* Changed $dbr to $dbcr for cluster reader

* Changed interpolated variables to bound parameters in db query.
Fix for misaligned icon pages
Merge pull request #204 from momijizukamori/release-1.13

Fix for misaligned icon pages
Merge branch 'release-1.13' into develop

* release-1.13:
  Fix for misaligned icon pages
(Bug 4719) Coerce all false values to the numerical 0

We can't rely on defined-ness. The cached value is stored as an empty
string when there are no points, so it fails the defined test and
doesn't get set to 0. Then in the frontend it gets printed as an empty
string...

This means that on production, or anywhere else with memcache on, first
time you load the page you'll get "you have 0 points". On subsequent
loads it becomes "you have points". Misleading! Annoying! Weird.
Merge pull request #195 from swaldman3/3994_deleted_account_pages

Bug 3994 : deleted account pages
Bug 4823 - Summertime: minor fix on Icons page
Bug 4824 - Abstractia: minor display issue on Icons page
Bug 4825 - Database: add shadow around icons on icons page
http://bugs.dwscoalition.org/show_bug.cgi?id=4823
http://bugs.dwscoalition.org/show_bug.cgi?id=4824
http://bugs.dwscoalition.org/show_bug.cgi?id=4825
-- Consistent vertical alignment in Summertime
-- Consistent display and vertical alignement in Abstractia
-- Add shadow effect around icons on Icons page for a consistent look
Adjust output of the pbadm script.
(Bug 4829) Fix authenticate() call and returned status

Two things:
* Fixed the method call (oh perl, you let us shoot ourselves in the foot
  sometimes)
* Explicitly set the returned status code instead of just the status
* line (see Bug 4832 for more info)
Merge pull request #209 from afuna/auth-digest-bug4829

(Bug 4829) Fix authenticate() call and returned status
Merge pull request #208 from ninetyd/release-1.13

Misc. Styles: minor fixes and improvements on Icons Page
Merge pull request #205 from afuna/disappearing-zero-bug4719

(Bug 4719) Coerce all false values to the numerical 0
(Bug 4826) Remember the previous security level after spellcheck

* for reasons related to changing minsecurity, we rebuild the security
  level dropdown with JS. We go back to the dropdown's displayed
  value only if it the user had already explicitly selected that level,
  rather than us having adjusted it because of minsecurity.

  See SHA: d1b7b5fa for a detailed breakdown of this case.

  Because we wait until the user has explicitly chosen a security level
  from the dropdown, this means that the value of the dropdown on load
  is ignored. This is not an issue when making a new entry
  (minsecurity), and not an issue when editing (that code path is not
  triggered on edit), but is an issue when spellchecking (the initial
  value *has* been explicitly selected by the user).

  This is much longer than the actual code, but the solution then is to
  mark the form as having been spell-checked, and then trust that
  initial value as being one the user chose deliberately.

* also removes a couple TODOs re: spellcheck which are no longer
  relevant since spellcheck is handled for those cases