Currently when requesting to cook archives from the browse web application, the list of created cooking tasks are
cached on a per session basis (using the Session Storage API from Javascript). This means that if the browser (tab) gets
closed, all tracked tasks are lost and will not be shown again when reaching swh-web/browse again in a new session.

In order to improve the user experience, this tasks list should be cached across browser sessions (using Local Storage API
from JavaScript) in order to be restored each time swh-web/browse is reached.

As a side effect, this means that the user must be able to remove (partially or entirely) tasks contained
in it, otherwise it will grow indefinitely.