ENH: Identify and fix item ID collisions on startup

[HailStorm32]

Is your feature request related to a problem?

In a quick scan of the NU database, it was found that there were 70 collisions when looking at the item ids in the character xml.

Describe the solution you'd like

Have the server on startup scan the database for item id collisions, and fix any that are found. Should also log where the collision occurred and how many total collisions occurred.

Repository breaking implications

None

Describe alternatives you've considered

Not optimal, but scan for collisions before using an ID.

Additional context

Results of scan
collision.log

[EmosewaMC]

solution to problem: re-do how ids are done for items and remove the persistent bit
solution to the now colliding ids: one time migration to generate a new id for all non-unique ids alongside setting persistent objectid tracker base to the 32 bit unsigned integer cap