Update SafeHtmlValidator to match content_models

Updated the validator to match the SafeHtml validator used in govuk_content_models this should be pushed to govuk_content_models in order to remove the duplication although it will create a breaking change. The main difference here is that the version in govuk_content_models validates all fields on an object no simply a specified field. This works much more like a railsesque validator and only validates a single field.
Rename SpecDocAttachProcessor more meaningfully

The SpecialistDocumentAttachmentProcessor does not need to be specific to Specialist Documents. It is actually a markdown processor specifically for attachments.

Similarly, in the wiring, markdown_processor is not accurate, this only deals with attachments so we will rename it to markdown_attachment_processor.
Rename SpecDocGovspeakToHTMLRenderer

As with the MarkdownAttachmentProcessor this is no longer specific to specialist docuements, but is actually reasonable to use with anything which responds to a bady method which returns something containing Govspeak.
Add body attribute to manual edition
Allow manual body to be previewed, edited and shown

Adds new routes for previewing the govspeak body and adds a form element for creating and updating the body attributes. Also displays the body govspeak on the show page
Export manual body as html to the content store

Before sending our govspeak body to the content store, prerender the govspeak as html
Rename updated_at to last_update
Merge pull request #250 from alphagov/rename-updated-at-to-last-update

Rename updated_at to last_update
Remove a commented out method
Merge pull request #251 from alphagov/remove-commented-out-method

Remove a commented out method
Merge pull request #246 from alphagov/feature/related-links-for-manuals

Related links for manuals
Remove content api from manual publishing pipeline

Manuals are no longer published to content api but instead published to content store via the publishing api. This is a first step towards removing content api.

with @tommyp
Export to publishing api before rummager

We should publish content to content store before publishing to search. This is so that when something arrives in search there is no way a user can reach the page before the content is available in the content store
Merge pull request #254 from alphagov/remove-content-api

Remove content api from manual publishing
Remove Finder API integration

Now that Finder Frontend is pulling results from Rummager we don't need
to update Finder API when documents are publishing nor withdrawn.