QC of new Ubergraph builds

What kind of QC should we have in the Ubergraph build? Right now there is very little. If the build completes, and the database is about the expected size, I deploy it. I save the previous database file so that we can easily roll back if a problem is noted.

I can imagine adding some queries that are run against the new build and against the live endpoint, checking that counts haven't decreased.

@dosumis @matentzn any ideas?

No files, tests, or entry points are named. Start by reviewing how Ubergraph builds and deploys its database and how the live endpoint is checked; done means having agreed QC checks that compare the new build with the live database and define when deployment is safe.

Written by the indexing model from the issue text.