[East Sussex] initial work on cobrand and templates

 - Get layout, including map working
 - Identified major clash point for CSS
 - Move eastsussex resources locally (in part to be able to override
   clashing names like .container)
[East Sussex] Tidy up layout

 - Tidy up layout of a few elements on front and map pages
 - ensure example places are within county
 - match council website body width
 - Remove 'size2' class from body
   This means we don't need lots of little CSS hacks to tweak things back into position
 - Restore 'contact us' underline
 - Ensure content extends down to footer
 - More UI layout tidying
 - Make sure error and confirmation pages don't have obscured content
 - Improve display of frontpage header on mobile
 - Better CSS selector for header display on mobile
 - Fix display of map on mobile
 - Tidy up display of footer buttons on mobile
 - Put mobile-specific styles back into base.scss
 - css separate margin-top for map/twothirds pages
 - Fix display of languages in footer on mobile
 - Removed unused CSS files
 - East Sussex doesn't have tracking_code.html, so remove reference to it
[East Sussex] Build templates from fragments published on eastsussex.gov.uk

 - Update styles to handle new templates
 - Ignore built templates
 - Ignore downloaded template fragments
 - Put East Sussex CSS before FMS overrides
 - Allow template build script to be run from outside its directory
 - Add file-watching capability to East Sussex template building script for local dev
[East Sussex] map and nav cosmetics

 - Use East Sussex-specific position_map.js
 - Display map correctly on desktop
 - Increase default zoom level and use correct grammar for postcode box
 - Tidy up default font size and center elements on postcode form
 - Correctly position report form, allow links in sidebar to be seen
 - Make map guidance text visible on mobile
 - Fix display of site header across all pages
 - More sidebar/header fixes
 - Override some text on the report sidebar to be more friendly
 - Remove unused images
 - Use breadcrumb bar for main nav on desktop
 - Restore correct background colour to footer
 - Tighten up vertical spacing on all pages
 - Slacken vertical spacing on home page
 - Stop the sidebar clobbering the footer
 - Tidy up menu display
 - Ensure form errors are shown properly
 - Add greeting and 'sign out' link to appropriate place
 - Ensure correct width is used on IE8
 - Make 'home' breadcrumb a span instead of a link
 - Hide top 4px border on mobile
 - Remove breadcrumb styling from FMS nav
 - Use ellipsis and correct capitalization on confirm page
 - Don't uppercase all button labels
 - Hide email icon in email fields
 - Don't italicise input placeholder text
 - Use correct font family, alignment and size for various elements
 - Correct box shadow, fix pin alignment, various UI fixes
 - Ensure font size isn't too small. Fix header on wide but small screens
 - Don't adjust .content height for East Sussex pages
[EastSussex] tweaks after comments from ESCC

 - change front-page text
 - rename Category to Type
    By overriding report/new/category template snippet.  This is hacked
    in (including substitution of the "-- Pick a category --" text, as
    not sure how to simply do this as a cobrand-specific translation.
 - hide footer on mobile view
 - pothole field input and display
      This is a temporary request, which we hope will be superseded by
    full integration in due course.
      A command is documented in the cobrand to set the "extra" on the
    contact info for the Potholes category.  This is then displayed by
    the UI.  The default process_extras places it in extra, for
    potential future processing.
      As this is a temporary fix, we are calling this field
    "detail_size", as this is automatically included in "Details" and
    therefore also sent in the email.
      (This means that we may need to update data later on to call this
    "pothole_size" or similar in future?)
 - contrast tweaks (Via request from Matt Tooke at ESCC.)
   Not all handled precisely as he suggests:
    * spacing of button nav -- more or less as suggested, but tweaks for
    the <span> selected button, and reduced padding on non-frontpage.
    * sign-in buttons: fixed using CSS for .green-btn instead of adding
    HTML class throughout.
    * mobile-footer: edited <footer> css, as suggested by Dave Arter.
 - revert problematic CSS (breaks map report page)
 - Remove spurious "FixMyStreet" button
 - frontpage subheading wording
Let cobrand override geocoder

Fixing issues with Bing geocoding for East Sussex,
for example "Church Street".
Merge branch 'east-sussex-candidate'