Move questions config things into config.py

from question_config.py and __init__.py.
[bug 936718] Implement infra for question statuses.

* Adds model manager to get questions with the following status:
** DONE
** RESPONDED
** NEEDS ATTENTION
** NEEDS INFO
** ESCALATED
* Adds helper to question model for setting and unsetting NEEDS_INFO.
[bug 939164] Fix product/topic edit form when one is missing.
Fix up qunit tests.

* Remove $(function()) wrapper. It isn't needed since the JS is added at
  the end of the HTML file.
* Fix a bunch of jshint problems.

Not all the tests were running. In particular, the browserdetect tests
weren't running. They are running now.
[Bug 915686] Make browserdetect.js understand fxos
[Bug 915686] The great showfor rewrite of 2013.

Rewrites showfor to be harder/better/faster/strong. More particularly,
data is pulled from the database instead of a config file, and the logic
is smarter to support more products. Less special cases and less
logic headaches!
Remove sourcemap error from jquery.
[bug 923732] Create a badge list page
[bug 889467] Nix verify_exists arg

The verify_exists arg was removed from URLField in Django 1.4. Using it
kicks up an error in Django 1.5, so I'm taking it out.
[bug 946321] Fix the /kb/new page.

The slug field was conflicting with the document form.
Fix some showfor macro calls.
Make "Customize this article" localizable.
[bug 946695] Products are inherited from the parent.
[bug 946695] Use document.get_products() instead of document.products.all().
[Bug 946267] Showfor: be less clever in the admin.

Trying to stop duplicate default versions kind of broke the UX of the
admin, and having multiple defaults for one product doesn't blow up. Not
even a little bit.

Additionally, apparently you can't have '.' in SlugFields. You can
insert dots into them via migrations though. So that's weird.
Fix casing of Get Involved string for consistency.
[Bug 946267] Showfor: Code changes for TB support.

Most of the real work will be in the database via the admin.
[bug 947206] Change log_error to log_exception

Right now one of the strings is kicking up an error, but we have no idea
which string it is because there's no traceback. This changes the
log_error to a log_exception which will give us a traceback which
hopefully will make it to Sentry and then we should be able to track
down the problem string.
[bug 915559] Enable Serbian (sr-Cyrl) in AAQ/Support Forum
[Bug 947043] fix link position on profile