DBCHecker: Does it differentiate between field and info for archive information?

A dbload which had `field (archive, "VAL")` seems to have passed the db checker, but fails within the starting of the IOC as archive is not a valid field. We need to verify whether or not the dbchecker differentiates between these types of information and if not, we should extend the checker to warn if you have `field (archive`, or fail to have `info (archive`. Any other odd pairings should get their own ticket.

## Acceptance Criteria
* DBs with `field (archive, ...)` fail the db checker
* DBs with `info (archive, ...)` pass the db checker