These were reported by flake8 as "F401 [...] imported but unused".

This does not yet do anything without changes to dak.conf.

Postgres already checks non-null constraints for us.  It is not needed
to duplicate some of these checks in Python.

Newer SQLAlchemy versions seem to track the `binary` attribute of
`BinaryMetadata`.  This means the association proxy in `DBBinary`
would first create a `BinaryMetadata` with `binary` set to `None`,
flush this to the database and then set the actual value of `binary`
we want.  However the flush fails, as `NULL` is not allowed for the
`binary_id` column.

The problem can be avoided by not setting `binary` to `None`.  This is
treated as an "undefined value" by SQLAlchemy and changing it later
means the database row never sees `NULL`.

The same applies to the `source` attribute of `SourceMetadata`.

Maybe this check should eventually be dropped?

Signed-off-by: NJoerg Jaspert <joerg@debian.org>