In the POC, requests for user settings config maps go to the spoke cluster, which fails since the user doesn't have permission causing console to white screen. The config maps can be stored on the hub cluster. That allows general preferences like the selected language to be used regardless of the selected cluster and avoids problems where the console service account doesn't have special authority on the spokes. The hooks we have will need to always request the config maps from the hub. This likely requires adding an optional property to `useK8sWatchResource` to specify a cluster.

We might need to scope some preferences to a particular cluster. That is out of scope for this story, however.

cc christianvogt rh-ee-jonjacks