(Bug 2366) Move custom text data from S2 layers to userprops

This keeps custom text the same across layouts, instead of saving it per
layout.

-Creates new userprops to store the data instead of s2 props
-Creates a widget to handle recieving and posting of userprops
-Inserts widget into the Module section of Text options, maintaining
 striping and classes
-Migrates s2 props to userprops, if the user is not using userprops
(Bug 2366) Clean-up of unnecessary code
-removed warn lines
-removed unnecessary JS
-changed header to reflect that widget is basically new code
and only shares basic subs and variable names with other widgets
(Bug 5261) New style: Trifecta
-- Add new style w/ 15 themes
-- Add images
-- Add previews
Merge pull request #585 from ninetyd/bug5261/trifecta_newstyle

(Bug 5261) New style: Trifecta
Merge pull request #584 from afuna/bug4703-double-stylesheets

(Bug 4703) Fixes double-loading of stylesheets
Merge pull request #560 from momijizukamori/Bug2366/Customtext

(Bug 2366) Move custom text data from S2 layers to userprops
(Bug 5265) Convert /community/index to TT + foundation
(Bug 5265) Convert the list on /community/manage to TT + foundation

* moves the page from /community/manage to /communities/list
  The form elements for community settings at the bottom are still undone

* modifies the appearance and order of the links to be a bit less jumbled together

* converts from BML to a controller + TT

* converts to Foundation for greater consistency across the site
(Bug 5265) Split settings in /communities/list into their own columns
(Bug 5073) Don't use width:100% on #content

The #content element is nested and may have applied margins to it that
could cause scrollbars. So let's use nested-collapse instead of the
default.
(Bug 5265) 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 5265) 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 5265) 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
(Bug 5265, 5073) Add .row .columns container around page content

This is needed for all pages (to add space around the edge), so add it
to all pages.

Individual pages can still have their own per-section row/column
wrapper.
(Bug 5073) Create pagination template

Template meant to be included within other templates; goes into
views/components.