edgehog-device-manager
Expose the associated UpdateCampaign (if any) from an OTA Operation
Right now we have a boolean flag manual? which indicates if an OTA Operation was started manually or from an Update Campaign. We should expose the Update Campaign too, so that we can link back to it in the frontend. At that point, the flag would become redundant too since it could just be desumed by the presence of a linked Update Campaign
Actually, it makes sense to also leave the manual? flag as-is, since it allows us to decide if the OTA Operation needs to clean up its BaseImage without having to look at the Target schema (where the foreign key is stored)
Leaving this open since GraphQL now exposes the updateTarget of the OTA operation, if any, but the frontend has yet to use this information on the Device page to distinguish manual OTA operations from those created within an update campaign.
