Warn and/or handle situation where two recordings have the same recording_id but different application_ids

[jleibs]

Explanation

You can easily create some rrds like so:

import rerun as rr

rr.init("rerun_example_app1", recording_id="some_rec_id")
rr.log("hello", rr.TextLog("Hello"))
rr.save("bad1.rrd")

rr.init("rerun_example_app2", recording_id="some_rec_id")
rr.log("hello", rr.TextLog("World"))
rr.save("bad2.rrd")

If you open them in one order: rerun bad1.rrd bad2.rrd you'll see the recording assigned to rerun_example_app1
If you open them in the other order: rerun bad2.rrd bad1.rrd you'll see the recording assigned to rerun_example_app2

This has annoying consequences for things such as blueprint-assignment and general understanding for users.

Proposal

At a minimum, we should detect and warn in this situation.

It would be nice to make the viewer still as usable as possible here. The two possibilities most inline with user intent are:

• Place the derived joint recording with all of the contents in both apps
• Keep the individual recordings isolated within their respective apps

Additionally, it would be very nice if we had CLI tool to fix appliation_ids for existing recordings since once you're in this state it's annoying to fix and you don't want to have to re-log your data just to correct it.