Test database using two parsers on same input

[lwillmeth]

Both parsers should attempt to insert the same data, but only one should succeed. We'll need to test this by parsing the same audio to two of the pi zeros simultaneously.

[lwillmeth]

We talked about this as a team yesterday.

The undefined behavior is that right now, both parsers will insert every value. We'll essentially have two copies of each signal from the rocket.

I would prefer to have a single, more complete set of data by keeping only unique values. If both parsers see a data point, only one should succeed, but either parser can insert the data point. This could be implemented by making the primary key a combination of columns to prevent duplicates, or by using a more sophisticated insert.

Another idea is to just accept duplicates and handle them later. This would be easier and probably not mess anything up. Graphs can have two points in the same spot without looking bad.

[lwillmeth]

We're still waiting on access to the BeelineGPS telemetry transmitter and radio receivers.

[lwillmeth]

Yesterday we completed our first end-to-end test using two parsers on the same receiver. It worked!

(This was delayed due to not having access to the telemetry transmitters.)

We did need minor changes from 13bdd3d46f54037367e1c579997243b61ab42c88