Removing PK on validity_start_date for FootnoteAssociationGoodsNomenclature

This is to fix an error with the TARIC sync which failed on 2014-07-23
where a FootnoteAssociationGoodsNomenclature's validity_start_date was
being updated, this causes an issue because when updating we use the
primary key to fetch the record being updated. As the attribute being
updated was part of the primary key, the record was not found and
halted the sync.

We will have to review all other instances of validity_start_date in a
primary key to ensure that this doesn't halt the import in the future.
The TARIC Validator ROIMB4 should use the regulation_group_id not iod

This validation is trowing validation errors because it is using the
wrong key to look to the RegulationGroup
Add note to README about audit:verify for validators
Merge pull request #195 from alphagov/fix-ROIMB4-validator

The TARIC Validator ROIMB4 should use the regulation_group_id not iod
Merge pull request #194 from alphagov/fix-taric-footnote-association-gn-import

Removing PK on validity_start_date for FootnoteAssociationGoodsNomenclature
Fix README now plek is updated govuk_setenv is not mandatory
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