(Bug 5073 Convert /community/create to Foundation + TT

* now under /communities/new

* the creation process should be the same functionally, different
  visually (also differs in backend: using controller + view)

* adds $r->HTTP_SERVICE_UNAVAILABLE to DW::Request::Apache2, to emulate
  existing sysban behavior in non-BML contexts

* creates a [% form.radio_nested %] element to be used in place of [%
  form.radio %] on Foundation pages (different HTML structure)

* adds jquery.checkusername.js for general use when creating / renaming

* adds jquery.validation.js for foundation pages. Currently
  experimental. Adds error message display and handles ARIA flags

* adds htdocs/js/page folder for per-page JS. This should be fairly
  minimal, mostly initializing. Reusable modules should go into
  htdocs/js

* adds .journaltype-textbox / .$journaltype-textbox (e.g., div
  class="journaltype-textbox community-textbox") classes, to be used
  whenever we want the userhead in a textbox
(Bug 5073) Fix links to community/manage to community/create

* community/manage => communities/list

* community/create => communities/new

Redirect is in place, but no sense having an extra step.
(Bug 5073) Adjust styling of bullet points in tables

list-style-position: inside was causing issues with the table cell being
too narrow in chrome
(Bug 5073) Adds an error section to the top of foundation pages

See DW::FormErrors for instructions
(Bug 5073) Adds per-form-element error messages
(Bug 5073) Add a 1em left margin to all lists

* removes a 1em margin to lists in tables, since those no longer need to
  be special-cased
(Bug 5073) Use DW::FormErrors in the Community controller

This also acts as an example of how to use the DW::FormErrors object
in controllers. Note that it's really all in the controller -- the
display of the errors is handled by the site skin, instead of having to
be inserted per-page
(Bug 5073) Use existing .error elements when validating with JS

Previously, we just used js-generated .error elements; but if we have an
existing error (say from page load), and then they change the value, we
want JS validation to modify the existing error message