Enable users to add unresolved mappings

- Add a blurb about unresolved mappings and what the point of them is, when the option is selected.
- Mappings marked unresolved added through here get added, correctly, to the database with a type of unresolved.
- Show unresolved as archives in the mappings table, in muted style. Add a question mark with a hover to explain the unresolved type, but why it is marked as an archive and greyed out.
- Show current status when editing unresolved mappings, like we do for redirects and archives.
- Default the mapping type to unresolved in the `MappingsFromHostPaths` import rake task.

This has the side effect of allowing filtering by unresolved, in so far as it doesn't strip Unresolved from the list of type filters. Stripping it out, both with JS enabled and disabled, so that it could be constrained to a separate story, was quite a bit of effort in the end for not so much gain. This does filter by unresolved, but none of the other filtering stuff that was in @fofr's prototype - showing percentage of unresolved mappings - that's reserved for the separate story.
To clarify: we did understand it, but it took some effort. As part of the Postgres branch, I just addressed some tests which weren't explicit about their behaviour and required some (only a little, but some!) detective work. I think the Whitehall CSV spec has a similar issue - it's mostly about over-reliance on RSpec's nice shortcut `its(:thing)`. [This is how](https://github.com/alphagov/transition/commit/7838616671f87c4cdc2bda40dcdde9d113fc0481) I fixed mine to satisfy "don't make me think".