Loading saved respawn time messages spam during server startup

Description:

There are too many messages after update TrinityCore in server log when server is starting up connected to respawns.

Current behaviour:

There are errors after update TrinityCore in log when server is starting connected to respawns.
It does not get deleted after some time.
It stucks there every startup.

Expected behaviour:

There should not be these messages in so many count.
"Loading saved respawn time of XXXXXXXX for spawnid (XXXXX) - spawn does not exist, ignoring.

Steps to reproduce the problem:

1. Update Trinity to the https://github.com/TrinityCore/TrinityCore/commit/af874a211c0f064bd685cddeded3ca7d6d690e8f (from 4 months old core)
2. See the startup messages spam.
3. See log: https://pastebin.com/935UYizM

=> The structure of the logs is also wrong it seems - it says spawnid (0,302075) etc.
=> Should we truncate the table to fill it in with the correct data after server resets all instances?

Branch(es):

3.3.5

TC rev. hash/commit:

https://github.com/TrinityCore/TrinityCore/commit/af874a211c0f064bd685cddeded3ca7d6d690e8f

Operating system: Debian Linux 64bit

Start by reproducing the startup log on the 3.3.5 branch using the linked commit and compare the exact respawn-loading message with the provided log. Trace the startup path that loads saved respawn times; done means invalid spawn records no longer produce excessive messages and the spawn ID output is correct.