[fm] put sitrep analysis and input reports in the db when committing a sitrep #10505

We should stuff the (human-readable, JSON) representation of the fm AnalysisReport and AnalysisInputReport in the database when a sitrep is committed, so that they can be retrieved by omdb to display them later.

These are purely for human readable diagnostic purposes so they can just be wadded up into a big JSON and tucked away. They should be associated with the sitrep's UUID for querying, though.

We should delete these pretty aggressively once the sitrep is no longer current, as they probably get biggish kinda fast.