Move cache of unsaved changes in content library to local storage #17348
Description
This issue depends on #17347 to be resolved first.
Unsaved changes on the new code list page in the content library are currently saved in the state of the page component. They should be saved in local storage, so that the user can work using multiple windows, and come back to continue working later.
This issue is resolved when the content library stores unsaved changes with the utilities created in #17347 and #17346.