[fm] want provenance for rendezvous-created objects to include the sitrep version

Presently, when FM rendezvous creates an object (i.e. a support bundle or an alert) it is tagged with the IDs of the sitreps in which it was requested and created. These are intended for traceability when debugging (although in some cases I believe the presence of any non-null sitrep ID is used to indicate that something came from FM at all). It has occurred to me that it would be useful if these also had the version number of the sitreps in which they were requested and in which they were created. The version number can serve as a rough "about how long ago was this thing requested/created?" while debugging.

We could, potentially, turn the IDs back into version numbers by JOINing with the fm_sitrep_history table, and just do that in omdb when actually displaying a rendezvous object. However, we may not always be able to recover a version number from an ID, if if (as I intend to in #10904) we start deleting old sitreps from the history table. Therefore, it might be better if this was denormalized onto the records for the rendezvous-created objects, so that it could outlive the sitrep. I dunno.

Start by tracing FM rendezvous creation for support bundles and alerts, then inspect the fm_sitrep_history table and the existing sitrep ID fields on those records. Decide whether requested and created sitrep version numbers should be denormalized, and consider behavior when old sitreps are deleted. Done means rendezvous-created objects retain both version values for debugging.