Implement a mechanism to persist onboarding related data

Current implementation in MR-2 provides a way to onboard a device to wfx (i.e bind a clientId for the device that can be used to target a device for wfx workflows/jobs).

But this clientId isn't persisted anywhere (i.e in any DB). So, creating jobs for onboarded devices is difficult.