Add a workflow to publish tags

https://www.pivotaltracker.com/story/show/67644106

This changes Panopticon to add a workflow to publish tags. 

The content models bump (based on changes in alphagov/govuk_content_models#198) makes all tags draft by default, and adds a state machine allowing the tag to be published. Draft tags are now marked in the list with a pink 'draft' label, and then can be published from their edit pages. 

The state of an artefact for a tag (eg. a specialist sector) is kept in sync with the tag, so we won't ever have a 'live' artefact associated with a 'draft' tag. Additionally, the artefact edit form has been updated to support tagging draft tags to artefacts. The behaviour to prevent draft tags appearing in api responses has already been added to the Content API in alphagov/govuk_content_api#194.

The test suite has been updated to use the new `live_tag` factory where `tag` was previously used. Finally, the `OrganisationImporter` has also been updated to ensure all the organisation tags that it creates are in the `live` state.
No, it's used interchangeably across multiple apps. Whitehall uses `create` over `FactoryGirl.create` in most places, and then there are uses in [Signon](https://github.com/alphagov/signonotron2/blob/be1a8e55025e29775a78796acc83d35346d1115f/test/functional/admin/organisations_controller_test.rb#L6), [Maslow](https://github.com/alphagov/maslow/blob/66309463a1cdb93f857683aa6a34f411ed68e2f8/test/unit/user_test.rb#L41), [Contacts](https://github.com/alphagov/hmrc-contacts/blob/336ecbc1c3cd12bd244bba480289183e639b30d8/spec/support/shared_contexts/auth.rb#L2) and [Transition](https://github.com/alphagov/hmrc-contacts/blob/336ecbc1c3cd12bd244bba480289183e639b30d8/spec/support/shared_contexts/auth.rb#L2).

I think we're okay to use either form. In the test context, I think the repeated use of the `FactoryGirl` constant is pretty superfluous.