a large number of build targets breaks the save to db functionality due to schema misconfiguration

[trey-ivy]

looks like there is an issue that once you surpass a certain number of build targets, the query is no longer able to effectively seralize the build object to the database. further exploration reveals this is because I forgot to add some .Unique() annotations to objects in the schema, so instead of 1:many, they are many:many relationships, which is problematic in several ways.

I've got a fix in the works

[gempesaw]

i wonder if this is related to the segfault i was running into on #2 ! in my bazel invocations, i was trying to stream to bb-portal with ~5000 targets . i'll keep an eye out and try this fix whenever it's merged 🎉