Fix broken functional tests ...

Fix broken specs with random see 55679

Fix broken tests for random seed 19381

Temporarily disable travis security checks

Since I'm testing the specs, this should help make it faster

Fix bug caused by random Org locale

Fixes recurring issue with tests being loaded in German

Fix broken specs

Fix tests breaking with seed 60029

Fix broken specs with seed 12116

Fix broken specs with seed 51011

Fix broken template upgrades specs

Fix travis artifacts addons

Add Travis asset debugging

Remove Amazon S3 region from asset uploads config

Move S3 configs to local travis file

Re-add hygiene tasks to Travis YML

Disable broken test for now

Refactor tests for template upgrade customisations

Update tinyMCE helper to match capybara format

Refactor how section ordering is handled (#1837) ...

* Extract template customizations into own controller

* Refactor Template model methods

* Fix view logic in draggable sections

* Add button for customising phase

* Fix rubocop violations in GuidanceService

* Rename GuidanceService to GuidancePresenter

* Fix bug in phase preview order sections

* Refactor preview action/controller code

* Fix Section ordering in various views

* Fix rubocop violations

* Fix bug forcing Phases to be modifiable

* Fix broken tests

* Update method to check if section is draggable

* Extract copy action into its own resource

* Extract customization transfers to own controller

* Remove redundant routing condition

* Fix Rubocop violation issues

* Change condition for section draggable

* Refactor instance variable in PlansController

* Fix broken tests

* Add test support for 'de' locale

* Fix merge issue in plans controller

* Fix broken specs in plan#request_feedback

Fix TinyMCE JS on forms loaded with DOM (#1827) ...

* Fix TinyMCE JS on forms loaded with DOM

Fixes #1777

* Fix broken specs

* Fix Rubocop style violations

Ignored LineLength violations when string is part of FastGettext

* Updated rubocop style gem

Ensure annotations destroyed when text is blank ...

When a user updates an existing annotation to set its text to blank, this
should destroy that annotation record on the DB—since they can't be valid without
text.