Stop duplicating status strings for SUPPORTED_STATUSES
Rename SUPPORTED_STATUSES to be http-specific
Add a 'type' column to the three mappings tables

This column stores the mapping type as a word string rather than as
an HTTP status code string. There isn't an appropriate HTTP status code
to use for unresolved mappings, so this is the cleanest way to store
users' decisions about mappings in the long run.

The new column has the same null constraints as the existing
http_status column on that table in each case.

This commit also adds validations for Mapping.type and sets the type
from http_status before validation. The type is not yet being set
correctly everywhere, but all the existing tests pass.
Set mapping type when importing from Redirector
Add a test to document import of '418' mappings

We currently have 198 mappings in production with an http_status of
418, which Redirector used for 'pending content', to signify that
content was coming but was not yet published, so couldn't yet be
redirected to. Bouncer serves 404 for these.
Only set type if http_status is supported

This means that the standard shoulda matcher for testing inclusion
validation works, because otherwise it wasn't able to set an invalid
value without it being changed by the callback before validation.
Add a one-off rake task to set type for existing mappings

This took 22 seconds to run in dev with 636,459 mappings
(replicated from production earlier this week).
Preserve '418' http_status as 'pending_content' type

This isn't a valid mapping type, but we already have 198 mappings
with http_status '418' in the production database because they
were imported from Redirector. We should not lose this information
about these mappings when switching to using the new type column.
Use type instead of http_status in Mapping model

This is a first step towards this goal, and will have broken lots
of things. The mapping model specs pass right now, though...
Make bulk tagger view model specs pass again
Make mappings batch model specs pass again

Now all model specs are passing.
Make mappings_from_host_paths specs pass again
Make Whitehall mappings import specs pass again
Make MappingsBatchOutcomePresenter specs pass again
Make mapping controller specs pass again
Make helper specs pass again

There are some quite horrible things here, but at the moment I'm just
trying to get all the specs passing again. When I get onto the features
I'll have more of an idea about which helpers we actually need, and
will revisit this to make the helpers better.
Make the mapping index feature pass again

Also update two fixture steps which are also used in other features.
Make mapping filter feature pass again

Also update a fixture step which is used in several other features.
Make the mapping edit feature pass again

The specs for the ToggleMappingFormFields js module were not being
run because the filename didn't end 'spec.js', and after renaming
the file I found that 4 of those tests were failing (on master as
well as on this branch). I've updated the tests so that they look
ore up-to-date, but they are still failing and the output from
rake jasmine:ci isn't very helpful.
Make mapping_create_multiple feature pass again

And also hits_all as a side-effect.