Add foundation/base.scss to easily include settings/global functions

* foundation/base.scss should be included in pages or components if you
  need access to variables or functions. It won't print any extra CSS.
  This is important because before you had to explicitly set
  $include-html-classes to false... and I always forgot, bulking up our
  stylesheets

* tweak everything that imports foundation/settings or foundation/global
  to import foundation/base instead. Remove now-redundant
  $include-html-classes: false

* add a comment clarifying that foundation/foundation.scss prints out
  CSS and is for inclusion in site skins only
[#665] Convert the overall structure of /entry/new to foundation

* use alert-box instead of ui-highlight

* use foundation's grid instead of our custom resizing (does still
  require some custom logic because of the entry-partial-width versus
  entry-full-width)

* use button-bar/button-group instead of action-bar
Set the legend background to be transparent instead of body bg

So that it always works, even on different backgrounds (e.g., panels)
[#665] Overall component appearance
Move htdocs/js/page to htdocs/js/pages for consistency
[#665] Base JS
Use "clip" instead of left/top positioning for visually-hidden elements

This is to avoid issues with dotted outlines extending to the top of the
page when there's a focusable element
Adds foundation icon fonts

We should only use it decoratively -- that is, alongside text, but not
purely on its own.
Rename "screenreader-friendly" to "visually-hidden"

Seems clearer as to what it actually does
[#665] Collapse/expand without using jQuery UI
[#665] Collapse plugin tweaks

* make the generated button the outermost element, so that we don't have
  to override as much of the font styling

* remove some now-redundant CSS

* tweak the logic of isExpanded so it defaults to start with expanded
  (if no data was given)
[#665] Document the collapse plugin in /dev/style-guide

* which files to include

* how to load (adds a new "onload" block in template toolkit for
  convenience)

* what is important to include: data-collapse, optionally
  data-collapse-state
[#665] Shrink the components text a bit
[#665] Update form elements

* use "hidden" instead of "invisible" for the label class

* minor refactor: use dw.ml(foo) instead of [% foo | ml %] when setting
  labels
[#665] Add missing label
[#665] Put button bar in its own row so we're sure to clear components
[#665] Use DW::FormErrors for handling errors

* replaces @error_list with $errors; removes the code to print out
  errors on the page because this is handled automatically

* also adds DW::FormErrors->add_string, which lets you add a full string
  instead of the ml_key to the list of errors. This is useful for
  protocol errors and errors stored in variables (e.g., readonly error)
[#665] Stop using /update.bml and /editjournal.bml strings
[#665] Refactor DW::FormErrors to always have error.message

Instead of having to worry about whether we have the ml or the raw
message in the view, let's just let DW::FormErrors handle it. As far as
we're concerned we only need to worry about error.message (though the ml
and args are still available)
[#934] Show the edit entry again link unconditionally