Tracking issue for Omicron changes necessary to support and manage live migration.

Nexus

• Durable storage of live migration state (likely tightly coupled with the question "which sled does an instance live on")
• Client APIs for accessing Sled Agent API
• Decision-making engine for "when should we actually initiate this process"? Likely influenced by system load, system updates (see Update System: Tracking Issue #250), but we can make something super simple to start (or explicitly triggered by an internal API).
• (???) Any networking-related work to ensure that the source/destination propolis instances can actually talk to each other
• Validation of source/destination versions, to ensure that live migration between the two sleds is actually possible
• API + expanded instance state for "getting updates from the propolis instances that are actually doing the work of the updates". Nexus probably wants to be aware of "what phase of the migration are we in", and should be notified by source/destination.

Sled Agent

• Interface to initiate live migration (source propolis instance)
• Interface to initiate live migration (destination propolis instance). Presumably, the source/dest will talk between each other + send notifications up to Nexus as Propolis moves between stages of live migration, but interfaces will be necessary here for bootstrapping.