Revisit the optimisation introduced in
SERVER-43664 which effectively skipped checking and repairing log settings for WT tables at startup. This improved the startup time on deployment with a large number of tables, at the cost of not catching and resolving table logging inconsistencies. We have observed an incident where one such inconsistency was discovered long after it was introduced, and at that point it was hard to recover from.
This ticket is a more comprehensive alternative to
SERVER-68908 because it will also detect and resolve pre-existing inconsistencies.