[bug 842882] Fix wiki.js issue during minification
[Bug 846281] Search Form Refinements

See: https://bugzilla.mozilla.org/show_bug.cgi?id=846281
Some tweaks for search form on search page.
[bug 853975] Fix readied_for_localization traceback.
Delete ReverseProxyMiddleware and StaySecureMiddleware.

not used!!
remove StaySecureMiddleware

We now have HSTS so this is not needed anymore.
Update Rickshaw's jQueryUI.
Refactor some rickshaw code to be reusable.
[Bug 845775] Make KB helpful graphs use Rickshaw

This replaced Highcharts on the "Show Helpful Votes Chart" link in the
history of a KB article.
[bug 842882] Fix lazyloading on mobile wiki
[bug 829340] Remove contributor forum dashboard.

The welcome dashboard goes along with it as it only had the purpose
of tricking people to join the Contributors group so they could see
the contributor forums dashboard.
[bug 852733] Add script for adding emails to exit survey.

This is a script that will be run outside by sumo team, possibly on cron
from the sumotools survey.

It gathers emails from our email collection survey on SurveyGizmo and then
adds those emails to the campaign of our exit survey on SurveyGizmo.
[Bug 850215] Safe email translation.

I made a decorator that calls a function, and catches any errors that
might be localization issues. If one of these types of exceptions is
raised, it logs the request and sets the locale to English and tries
again. Then I found all the places where @willkg's `uselocale` context
manager was being used and converted it to a function that used this
decorator. In my testing this makes emails robust to localization
errors.

I tried to make this a modification to the context manager originally,
but to run the wrapped code again would require ugly bad horrible
bytecode hacks. So I decided better not do that. Luckily, this was is
generic enough that it might be reusable for web traffic too. I didn't
look into this very much.

I tried to log these errors in a way that will make them easy to work
on. I am assuming that we have Sentry/Raven configured to automatically
add stack traces. If this assumption is wrong, we will see that when it
goes to stage, and can add the stack trace into the error message.