Removing browser local storage - persistent Storage

Problem:

Currently anything that is "saved" is saved in local storage. Users that move from one machine or browser to another do not have a consistent experience.

Goal:

Develop a plan to be able to store User Preferences. Initial support doesn't need to allow users to manage those preferences, but things that are currently stored in local storage should be moved to persistent storage. This epic focuses on both the admin and developer perspective.

Why is it important?

1. We consistently hear that the fact that we are not utilizing persistent storage is a pain point for our users.

Exploration Results

1. Include in what's new RHD blog and consider for improved usability blog
2. Request for Dev to generate a list of what we are currently storing in localStorage by grepping the code. This will help for sizing, but can also be utilized as input for the next phase where we manage preferences via the console.
3. No UX needed

Acceptance Criteria

1. As a user, anything currently stored in local storage should be persisted, thus remembered when running console from a different device or browser.
2. Note that the list generated by dev should be added to the ACs so that stakeholders understand the breadth of the changes and need for testing

Design Artifacts

None needed. There is no change to the Graphical User Interface

Slack Channel

#tmp-user-preferences

Notes

This is necessary pre-work for User Preferences/Settings to come post 4.7