LPS-37434 Adding empty constructor to HttpPrincipal to support unmarshalling
LPS-37434 make LAR handling more robust
LPS-37434 SF - rename the variable (no changes)
LPS-37434 copy/paste from LayoutStagingBackgroundTaskExecutor (no changes)
LPS-37434 cut/paste methods from StagingImpl (no changes)
LPS-37434 cut/paste the publication (no changes)
LPS-37434 copy method from StagingImpl (no changes)
LPS-37434 Apply changes needed for remote staging
LPS-37434 keep code consistent with LayoutStagingBackgroundTaskExecutor
LPS-37434 Update backend to use the new background task executor
LPS-37434 use cmd
LPS-37434 Updating UI to fit the background remote staging
LPS-37434 The old way of reporting NO_LAYOUTS error won't work anymore due to the background task arrangement - refactoring the way we handle that error, and also cleaning up this error type, all export/import/staging processes are being transformed to background processes
LPS-37434 Keep exception. All of this will be thrown asynchronously, right? or do we validate before creating the background task?
LPS-37434 Manage error messages for the asynchronous task