Add scheduled obsid to commands, states, observations

[taldcroft]

Description

This addresses a long-standing issue that the kadi obsid reflects the as-run loads. In the case of SCS-107, the kadi obsid matches telemetry but does not allow easily connecting back to planned observations (in particular the vehicle-only parts that still run along with all the planning products).

During backstop ingest, this PR adds a new command row with type=LOAD_EVENT tlmsid=OBSID which is a copy of each type=MP_OBSID tlmsid=COAOSQID command, but with the SCS slot decreased by 3 so that 131, 132, 133 => 128, 129, 130. In effect this puts "scheduled ObsID" commanding into the vehicle loads so after an SCS-107 they persist.

This PR also adds a new conf.matching_block_size configuration variable. This is mostly useful for testing and development and is not intended as something users would change.

Dev Note

There is an issue right now with deployment and options for back-updating the commands archive. Because matching command blocks (500 commands) are required at the interface between archive and new (backstop) commands, conflicts arise and if there is a mismatch (old archive / new code or vice versa).

Interface impacts

• Adds new type=LOAD_EVENT tlmsid=OBSID commands.
• Adds a new column obsid_sched to the output of get_observations().
• Adds a new state key obsid_sched to query the scheduled ObsID.
• Adds a new conf.matching_block_size configuration variable.

Testing

Unit tests

• No unit tests
• Mac
• Linux
• Windows

Independent check of unit tests by [REVIEWER NAME]

• [PLATFORM]:

Functional tests

No functional testing.