config file /home/user/.kube/config does not use quotation marks

Describe the bug

We use the mobile phone number as the username, but the generated kubeconfig does not use quotation marks, resulting in an error when using the oc command

bash-4.4 ~ $ cat /home/user/.kube/config 
apiVersion: v1
clusters:
- cluster:
    certificate-authority: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
    server: https://172.30.0.1:443
  name: https://172.30.0.1:443
users:
- name: 18656157120
  user:
    token: sha256~F696KTgtysnKT-U9yjUZ2mTreR2Sc8EFTuOKMSJIEik
contexts:
- context:
    cluster: https://172.30.0.1:443
    namespace: tool-polaris
    user: 18656157120
  name: 18656157120-context
current-context: 18656157120-context
kind: Config

bash-4.4 ~ $ oc get pod
error: error loading config file "/home/user/.kube/config": v1.Config.Contexts: []v1.NamedContext: v1.NamedContext.Context: v1.Context.AuthInfo: ReadString: expects " or n, but found 1, error found in #10 byte of ...|","user":18656157120|..., bigger context ...|72.30.0.1:443","namespace":"tool-polaris","user":18656157120},"name":"18656157120-context"}],"curren|...

Environment

• Web Terminal: v1.2.1
• OpenShift Version: 4.8

When I add quotation marks, the oc command can be executed normally

bash-4.4 ~ $ cat /home/user/.kube/config 
...
users:
- name: "18656157120"
  user:
    token: sha256~F696KTgtysnKT-U9yjUZ2mTreR2Sc8EFTuOKMSJIEik
...

Start by tracing where the web terminal generates the kubeconfig and reproduce the issue with a numeric mobile-phone username. Compare the generated users and contexts with the quoted example, then verify that the resulting config is accepted by the oc command.