Log warning about insufficient retention time for DB history topic

The DB history topics need to have "indefinite" retention time essentially. We should check upon connector start-up time and raise a warning or even error message if the topic is configured incorrectly, e.g.:

• retention < 5 years
• compaction enabled
• more than one partion etc.

Might even be done async, so to not impact start-up time.