v1.1 - Fix race condition in tracking setup

Release 1.0 was functional, but would require the user to execute the tracking process twice, just after the database was created, and tables tracked for the first time.

Consequently it is suspected that relationship tracking was executing out of sequence, i.e. potentially whilst table tracking was still being setup.

A sequence of settimer operations has bene introduced to ensure that tracking waits for the database creation process to complete (10 seconds allowed), and that the tracking of various elements is executed in a known order.

The actual root cause of this issue, may well be an async/await issue. So this fix is somewhat speculative, but appears to do the job.