Reply to /v1/purge before restoring the state

Purging data is already a long operation and waiting the target state to
be restored before sending the response can cause the request to
timeout. With `reboot-required`, the response will never be sent
because a reboot will happen when restoring the state.

This change ensures the API response happens once purge is completed.

Change-type: patch

src/device-api/actions.ts

@@ -151,9 +151,6 @@ export const doPurge = async (appId: number, force: boolean = false) => {
 			keepVolumes: false,
 			force,
 		});
-		// Restore user app after purge
-		currentState.local.apps[appId] = app;
-		await deviceState.applyIntermediateTarget(currentState);
 		logger.logSystemMessage('Purged data', { appId }, 'Purge data success');
 	} catch (err: any) {
 		logger.logSystemMessage(
@@ -163,7 +160,9 @@ export const doPurge = async (appId: number, force: boolean = false) => {
 		);
 		throw err;
 	} finally {
-		deviceState.triggerApplyTarget();
+		// Restore user app after purge. Do not wait for the result
+		currentState.local.apps[appId] = app;
+		void deviceState.applyIntermediateTarget(currentState);
 	}
 };