Improve the UX of the clone operation #2290
Description
Cloning (Save As...) can be a heavy, long-running operation, because it requires cloning the dataset, publishing to Geoserver, publishing the new dataset and setting up all the permissions and metadata.
It is asynchronous by nature, and as such, it's queued along with all the other async operations happening behind GeoNode.
In this moment, the operation and its status are not tracked very well inside the UI. The UX is left to be desired because the user is not provided with the expected feedback about the status of the operation.
When the user clicks the Save As button, the only hint is the volatile "Cloning..." message reported in the top bar of the resource. If users navigate away from the current dataset or refresh the page, they have no way to know the status of the operation.
To me, two enhancements are required:
1 - When the Save As operation is executed, users should be redirected to the (will be) new dataset page. A "suspended" state will inform he user about the status of the operation until it is completed
2 - When any catalogue listing is loaded, the client should query the executions API to see if there's any pending operation for the current user, and notify it inside the cards (like we do for the Delete operation)