applying longest match strategy to timespan scanning

if a timespanliteral is followed by more identifier characters, it is interpreted as a number followed by an identifier rather than a timespan followed by the remaining characters of the following identifier
Major bugfix: thread should be able to reuse the database transaction if the lock is already held by it

this bugfix allows for nested calls to PersistenceManagerV2.write() from within the same thread. The transaction will only be opened the first time the thread called write() and will be closed when the last Write instance of the current thread is closed
Made persistence access less prone to causing deadlocks by applying a timeout while waiting on the write lock
Revert: applying longest match strategy to timespan scanning

if a timespanliteral is followed by more identifier characters, it is interpreted as a number followed by an identifier rather than a timespan followed by the remaining characters of the following identifier (reverted from commit 4c62e2f79f90f284fed15f750568b1986f001511)
handle rare case that sector was not created when updating portals
Improved jsonizing
some missing classes
fixed bug in ObjectChecker
basic version of memory fleet tracker