Expose internal OTA campaign failures via API/frontend

Currently if a target update fails before its OTA Operation is started (e.g. unsupported starting version), the reason for the failure is not exposed to the user and it's just logged. We should instead expose it to provide a better feedback for the OTA campaigns.