Update database seeds with the dummyapiuser for development

The gds-sso gem mock MockBearerToken strategy if it cannot find a user
will call dummy_api_user.save! Sequel defaults to raising exceptions
when save fails and doesn't have a save! method, we could alias it
but adding the dummy user resolves the issue.

https://github.com/alphagov/gds-sso/blob/master/lib/gds-sso/bearer_token.rb#L56
Remove FACTER_govuk_platform from code.

In all of our current multi-vm environments:
    `ENV['FACTER_govuk_platform']=='production'`
Which means it's exactly the same as Rails.env

This commit removes it from the code.
Merge pull request #181 from alphagov/remove-govuk_platform

Remove FACTER_govuk_platform
log sql queries by day on sync
do not use transactions on sync process
use separate log files for each update type
ensure we unsubscribe from sql queries

so we don't log repeatedly each query
capture exception message on sync failure
sync: log conformance errors if they happen

also send them via API to see them on admin