Fix fatality notice casualty field duplication

www.agileplannerapp.com/boards/173808/cards/8196

this issue seems to have its roots in this refactoring:
https://github.com/alphagov/whitehall/commit/3b8145

the remove button handler script adds an additional
hidden field '_destroy' to the form with value true,
which should be sent to the server, which was not
the case. instead this extra hidden field was being
sent to the server.
Add unarchive_edition data hygiene task

'Unarchives' an edition by creating a draft from the original and
publishing it. The original edition's state is updated to 'superseded'.
Add additional notes around skipping of editions

Once the draft stack is up and running, it is likely that we'll want to push out
draft content too so that it can be previewed.
Export topic tagging changes to csv
Import csv tagging changes from csv

- create a script that will read from the a csv location passed as and
  argument and change the topic tagging for the content
- this script should also register the documents with panopticon,
  publishing_api and rummager
- add the document id and type to the csv to allow for easier reporting
  later
TagChangesExporter to take a file location
Create rake tasks to run topic tagging changes
Remove old topic retagging scripts
Use the passed source_topic_id in the csv build
change the update_type for the PublishingApiWorker to 'republish'
Use PublishingApi.republish method for registration
Make Publishing API presenters locale aware

The presenters present the instances appropriately for the current locale.
PublishingApiWorker can publish specific locales

Now that the presenters are locale-aware, the worker can push a content item to
the Publishing API in a given locale, defaulting to the default locale
otherwise.
Publish all translations to the Publishing API

Whitehall::PublishingApi.publish and Whitehall::PublishingApi.republish now send
all available translations to the Publishing API.

Note that these methods will now blow up if handed a non-translatable model, but
as we are not yet sending any non-translatable models to the Publishing API,
it's impossible to write a test to support this behaviour. That can be done at
the appropriate time.
Data migration to republish all translated things
Delete erroneously synced users

Signon push update rake task pushed information
of users who had never used Publisher, so cleaning
that up. see related:

https://github.com/alphagov/signonotron2/pull/290/files
Merge pull request #1862 from alphagov/fix-casualty-fields-duplication

Fix casualty fields duplication
Merge pull request #1882 from alphagov/fix-erroneously-synced-users

Delete erroneously synced users
Refactor after comments

- Use document id and document_type in the generated cdv
- Look up document with id
Permit :id for nested attribute fatality notices

Following-up on:
https://github.com/alphagov/whitehall/pull/1862

I missed adding this important bit of the fix,
which permits the `:id` of the destroyed nested
attribute, allowing rails to retreive the correct
associated record and destroy it.

The earlier PR already contains an integration
test to test this behavior.