Gateway: Saving configuration errors when config file has no preferences entry.

[adietish]

Describe the bug

In Gateway plugin you have to provide cluster and token in order to log in. If you update the token, you can have it update your configuration. If the configuration is missing a preferences entry, saving fails with an error.

This was reported at redhat-developer/devspaces-gateway-plugin#247 (review). It already occurs in the released plugin version 0.0.15.

Che version

7.116@latest

Steps to reproduce

Steps:

1. ASSERT: have a kube config file that is missing preferences

apiVersion: v1
kind: Config
current-context: dogfood
clusters:
- cluster:
    insecure-skip-tls-verify: true
    server: https://api.XXXX.openshiftapps.com:6443
  name: sandbox
contexts:
- context:
    cluster: sandbox
    namespace: adietish-dev
    user: sandbox
  name: sandbox
users:
- name: sandbox
  user:
    token: sha256~XXXX

(it's missing preferences: {})
2. EXEC: in Gateway plugin: use the suggested server, update the token and check "[x] Save configuration"
3. EXEC: click "Check Connection and continue"

Result:
You get an error dialog getPreferences(...) must not be null. Wizard wont proceed to the next step.

Expected behavior

your config should be updated to the new token

Runtime

other (please specify in additional context)

Screenshots

No response

Installation method

other (please specify in additional context)

Environment

other (please specify in additional context)

Eclipse Che Logs

Additional context

Gateway plugin 0.0.15