Refresh Primo's record of a device from the MDM
Pull ONE device’s current state from the MDM into Primo — hardware and OS details, disk encryption, users, compliance and MDM/EDR status — and refresh the labels and assignment suggestions that depend on them. This is the Primo side of a device refresh: refetchDevice asks the device to re-report to the MDM, this brings what the MDM holds into Primo, so after a fix the two together make getDevice answer with reality. Prefer this after any change made outside Primo; to refresh only the Primo-managed software rows, use syncDeviceSoftware. EXPENSIVE — do not call it in a loop or across a fleet: one call runs a full MDM sync and queues label, device-user and assignment-suggestion jobs behind it. Call it once for the device you just changed, then re-read getDevice. Set forceEnforcerExecution to also re-run the MDM control enforcers and re-fetch the disk encryption key — slower still, and it can queue commands on the device.