Support analyzing multiple builds (by incorporating directory into the table indexes) #36
Description
The current analyze schema assumes that only a single build is being analyzed, making it harder to compare builds.
Currently if you try to analyze multiple builds there are SQL exceptions thrown.
In particular it expects that the SerializedFiles names are unique (e.g. only one "level0" or only one version of a particular asset bundle).
I think we could adjust the schema so that the directory where the archive or serialized file is incorporated into the tables as a way to distinguish builds. E.g. the key to the directory would be added into the serialized file table and index would be on that key plus the Serialized File name.
One challenge is dealing with references between serialized files. The reference records the name of the serialized file. To resolve that reference properly we have to track the context of which directory is being scanned, e.g. assume that references only point to files inside the same directory.
Once working additional examples should be added to the documentation showing how to query just a single build and how to do some basic comparison of builds when they are inside the same database.