Option to save user settings separate when using local bridge

Description

As a developer of console, we often use a local bridge and running it as kube:admin. With the new ODC-4370 User settings feature it can be confusing if we all share one ConfigMap for our pinned resources, quick start process and so on.

As a developer I want to keep my user settings separate from other developers.

Acceptance Criteria

1. Developers can (easily) use save their user settings in a separated area.

Implementation idea #1

1. Provide a bridge parameter to prefix the user settings configmap with a string. BRIDGE_USER_SETTINGS_PREFIX ?
2. Automatically set this parameter in oc-environment.sh script to the current environment variable $USER
3. Use this parameter in api calls /api/console/usersettings to create prefixed ConfigMap, Role and RoleBinding
4. Provide a new SERVER_FLAG "userSettingsPrefix"
5. Extend the user settings hook to use the SERVER_FLAG to watch the correct ConfigMap as well.

Implementation idea #2 based on Christians and Sams feedback

1. Provide a user settings cli parameter to use localStorage instead of ConfigMap
2. Automatically set this parameter in oc-environment.sh script
3. Provide a new SERVER_FLAG {{"userSettings" and e}}xtend the user settings hook to use this flag to use existing localStorage fallback

 Additional Details:

None