Move diligency table to bottom of page.

Not that useful in most cases, only if you wanted some admin
competition on category entering/checking. Fixes #739.
Tweak summary output on bodies page.

Show more detail of unconfirmed/deleted categories; highlight and warn
if no categories, or if all categories are deleted. Fixes #516.
Couple of tests missing MapIt override.

Looks like Travis doesn't like connections back to itself.
replace Mailman cross-sell with Mailchimp signup form
Validate category name/email/note in admin.

This prevents the creation of a category with a blank name. Fixes #556.
Prevent overhang of admin body categories table.

Group things together more simply. Fixes #738.
Merge remote-tracking branch 'origin/issues/516-body-warning'
Merge remote-tracking branch 'origin/issues/739-move-diligency-table'
[FixMyStreet.com] Add information for councils.

Fixes #765.
Update links to point to new /council page.
EastSussex: set is_two_tier

I appear to have left this commented out.  Comments from both ESCC
and a district council (Wealden) on same day seem to point to this
as root of error.
ESCC. bodies_clause specialisation

patch for https://github.com/mysociety/FixMyStreet-Commercial/issues/603
more generic fix to follow
UK. Generic problems_clause for two-tier councils

Replace copy-pasted problems_cause declarations in Hart,
Oxfordshire, and East Sussex with a generic override in
UKCouncils.pm (as a bonus also overrides Stevenage)
[fixmystreet.com] correct pricing for back end scoping
Copy changes, add new FMS deploys

Conflicts:
	templates/web/fixmystreet.com/static/council.html
Paginate admin search results.
Merge branch 'issues/commercial/603/generic-problems-clause-for-two-tier'
[Warwickshire] cobrand work

First Warwickshire styling

 - imported WCC's header and footer files
 - Use Warwickshire colours for page elements
 - Include FMS elements in header
 - Use correct Warwickshire colours on map
 - Use full-screen map on desktop.
 - Improve display of homepage elements
 - Ensure correct classes are added to body tag
 - Make sure site header has correct height on front page
 - Tidy-up of unused header content and wrappers
 - Improve display of map
 - Position map beneath other elements

Improve map display

 - Take some CSS from Warwickshire styles to ensure its applied
 - Fix container widths on map page
 - Make sure map wrapper is the correct width
 - Add style overrides to match  Warwickshire.gov.uk
 - Ensure map controls are visible

Nav and mobile styling

 - Make sure sticky sidebar nav is usable
 - Improve mobile front page
 - Ensure map is full-screen on mobile
 - Improve front page display on mobile
 - Fix map display on desktop
 - Fix Warwickshire and FMS nav on mobile
 - Add viewport meta tag for mobile devices
 - Tighten up vertical spacing on front page
 - Fix header height on tablet size screens
 - Set pan/zoom position in CSS, not JS

Styling tweaks

 - correct styling of nav for wider screens (previous hidden by media query)
 - Add draft Warwickshire FAQ
   - Fixes https://github.com/mysociety/FixMyStreet-Commercial/issues/611
 - Warwickshire. remove all reports link as requested.
   - see https://github.com/mysociety/FixMyStreet-Commercial/issues/609
 - Update WCC footer
   - see https://github.com/mysociety/FixMyStreet-Commercial/issues/597

Bring WCC css locally, and override

 - Override for
   https://github.com/mysociety/FixMyStreet-Commercial/issues/612

 - favicon
   https://github.com/mysociety/FixMyStreet-Commercial/issues/616

 - update contact details
 - custom FAQ

 - fix padding on mobile
   https://github.com/mysociety/FixMyStreet-Commercial/issues/617
Open311 Endpoint

Subsystems include

 * ::Spark encoding conventions for xml/json
 * ::Schema using Rx to validate form of inputs and outputs,
      including validation for, e.g., dates and CSV as part of Open311

Handles following paths:

 * Open311 attributes for Service Definition
   http://wiki.open311.org/GeoReport_v2#GET_Service_Definition
 * POST service request
 * GET Service Requests
 * GET Service Request

Objects:

 * ::Service
 * ::Service::Request
Open311 Endpoint mySociety extensions role

 * Get Service Request Updates

This requires a new object ::Service::Request::Update, which of course
is not part of standard spec.  So, in order to make the core not too
contaminated by :

 * the endpoint should instantiate ::Service::Request::mySociety objects
 which know about updates
 * have added a learn_additional_types callback from Schema to Endpoint,
 so that core doesn't need to know about /open311/service_request_update
 * (but ::Spark knows about the exception for updates... meh, but is 1-line)