Refactor QUESTION_TYPE_TAXONOMY contanst in ViewAndEditTable into an application-wide constant providing the main categorization taxonomy per item type.

Refactor views into multiple files prior to developing edit item features. Also changed the edit/create item urls.

Only display the Remove Question Type menu item on pages where the
question type can be set.

If there is no source set on the tab configuration, the upload
button will no longer be displayed.

So user is redirected to the correct page after uploading data

Refactor the ViewsItems view, which covered the view and edit table, into a separate (non-view) class under tabs/view_and_edit_table.py. When ready, this will plug straight away into the new tabbed page functionality - in the mean time there is a place holder view to display the view where it used to be found.

Allow the chart count widget to have a time period. When present, apply the time period and display a legend detailing what the time period is.

ViewItem.get_category_options should return the options as we want them - we shouldn't have to process them later. So make sure it returns (short question, short question) as we want both the value and the text to use the short version.

Refactor add_items_categories and add_categories into a single call, and make the taxonomy slug configurable at that level (it's now hard-coded in process_items). Update tests to match the change and ensure we can update multiple items at the same time.

Re-introduce the per-row drop down to update each record's category as well as the mirrored buttons at the bottom of the page. This means that we have a single form that can either do a batch update, or an update of values set per row. The different action is determined by the submit button that was used - which is always named 'action'. Because we have a mirrored select drop down for the batch action, we need to know which one to take into account - so the value of the submit button indiciates which one was clicked, of the form <action>-<placement> (eg. save-top) and the name of mirrored inputs indidicate where they are located, of the form <name>-<placement> (eg. batchaction-bottom). The ViewItems class has a static method to find the active placement and rename the parameters accordingly. Some of the old code was re-introduced, though some of it was refactored (eg. what used to be get_categories, to fetch each row's selected category, has been moved to ItemTable to parallel get_selected, and is now named get_row_select_value (it's a more generic version, looking at the future when we'll update the region with the same mechanism.)

Now if a user attempts to log in from a login page with a stale
CSRF token, they will be redirected to the dashboard or, if they
have logged out, to a fresh login page.

Add tests for what happens when `add_categories` gets called with nonsense items and category names, should fail gracefully
https://trello.com/c/fWrvZDau/77-clear-out-technical-debt-from-working-on-taxonomies

Rename select_action to select_item which makes more sense. Rename the checkbox itself select_item_id to allow other types of selectes in the future. Move the code to determing selected items into ItemTable since this is where the form is generated, and we know how it was build.

Refactor the 'select all checkboxes' javascript into a separate file so it can be used on other tables easily. Add a test for the select all checkboxes javascript. Remove the label from the 'delete' column (which is now a 'select all' column as we may have other actions) and move it to the first column as per balsamic mockups.

Add add categories method to hid/views and call from process items

Has a test, but so far only for the single category case.

Use django_assets to manage our assets and ensure we can minify js/css, compile less files, and merge all js/css into a single file. For this to work in production, all assets must be statically defined in his/assets.py. To ensure the correct js/css is included, views can invoke hid.assets.require_assets which will raise an exception if the asset is missing. This also has the advantage of making clear which part of the code depends on a given asset. The admin command in django_asset library's latest release does not work with the latest Django - so we use a version pulled from git. See https://github.com/miracle2k/django-assets/issues/52