GitLab

This gives remote devices a control point to connect to the remove device
before having the information ready for the caller.

This object is meant to collect information about a device that we can
put behind an async function to collect it. That allows us to cleanly
abstract the process of connecting to a device before we know about
various architecture and OS information.

This doesn't activate anything yet, but let's us play around with UI ideas
on how we want the integration to happen.

This tracks the IdeBuildManager:device property and ensures that we have
it attached to our build pipeline. Currently nothing is using this, but it
gets us started towards hooking up cross-compile runtimes and deploy
strategies to get bits onto devices.

What would be really nice is if we could run an itimer which could change
a volatile after 1msec completes, or something to that nature. But for now,
let's just start to divide and conquer to find out what value works best
to keep us interactive.

As we progress towards bring device outside of configuration and into the
device manager, we need to update the pipeline when the device changes.

This ensures we reset the build pipeline (however the pipeline does not yet
set a device for the pipeline).

This allows us to set the device using the device-manager.device
action and the state as the id of the device.

This also changes our ABI while we still can to be more sensible
in getting a device by id.

I'm not sure how we're hitting this, but there are cases during shutdown
where we get into a sort of indirect life-cycle issue here. Possibly
the object gets invalidated during emission without our closure being
invalidated.

We should at least give the user some indication that the reason
there might be build issues is that the configuration is not
ready for use. This can happen when the device or runtime are
missing.

This can happen if the build device is not ready.

This allows tracking if the current configuration is ready for
usage with the ready property. This may be useful in UI to
notify that there are configuration issues that could be
effecting the build pipeline.