For performance, this is a best practice.

We already do this for our own JS, which includes jQuery. Howover, some
form JS needs jQuery, so it needs to be loaded after jQuery.

See: zsiciarz/django-markitup#25

django-markitup renders inline JS in each widget that configures the
widget. This JS requires jQuery and markitup.js to already be loaded,
which isn't the case if we're loading JS in the foot of the page.

So, override the template that generates that inline JS, with something
that generates a hidden tag containing only config. Then come back at
the end of the JS loading, and configure the widgets.

I'll do a similar PR upstream and hope that we can pull this out, later.

We have to load jQuery for it, which means double-loading it outside
admin. But at least they'll be the same versions now...