Add transaction/coordination ID to configure requests and logs

Why now? Not immediately critical, but easier to implement the earlier we start

Scope: All LMCs

Quality: Monitorability, Debuggability

The idea is that we introduce IDs that are used to correlate actions taken by different elements to bring the system into a new state. This would be added to logs to facilitate bringing logs from different elements together.

This came up in the context of the Configure command, specifically to CSP. It was felt that neither the scheduling block ID nor the scan ID are sufficient here to uniquely trace the actions taking by CSP during the configuration phase.