CORE-209 do not generate lock table creation twice when producing an SQL file

When generating an SQL file with updateSQL or changelogSyncSQL on a database that has no LB Metatables, the create and initialize statements for the lock table are generated twice to the resulting file.
The check for hasDatabaseChangeLogLockTable is not done in hasDatabaseChangeLogLockTable() as listLocks() would e. g. also be affected.