[release-v3.3.0] ks-console image OOM on arm64 platform

[niconical]

Describe the bug I cannot install KubeSphere V3.3.0 on my ARM64 machine, due to OOM in ks-console image.

For UI issues please also add a screenshot that shows the issue.

Versions used(KubeSphere/Kubernetes) KubeSphere: v3.3.0 Kubernetes:

{Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.10", GitCommit:"eae22ba6238096f5dec1ceb62766e97783f0ba2f", GitTreeState:"clean", BuildDate:"2022-05-24T12:56:35Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/arm64"}
{Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.10", GitCommit:"eae22ba6238096f5dec1ceb62766e97783f0ba2f", GitTreeState:"clean", BuildDate:"2022-05-24T12:50:52Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/arm64"}

Environment How many nodes and their hardware configuration: 1 master：64 cores/64GB Memory OS：OpenEuler 20.03(LTS) CPU：KunPeng 920

[root@node1 logs]# kubectl get po -A
NAMESPACE                      NAME                                               READY   STATUS             RESTARTS      AGE
kube-system                    calico-kube-controllers-69cfcfdf6c-b7pzb           1/1     Running            0             18m
kube-system                    calico-node-rd4z8                                  0/1     Running            0             18m
kube-system                    coredns-5495dd7c88-7kjcz                           1/1     Running            0             18m
kube-system                    coredns-5495dd7c88-ttk7s                           1/1     Running            0             18m
kube-system                    kube-apiserver-node1                               1/1     Running            0             18m
kube-system                    kube-controller-manager-node1                      1/1     Running            0             18m
kube-system                    kube-proxy-gx22w                                   1/1     Running            0             18m
kube-system                    kube-scheduler-node1                               1/1     Running            0             18m
kube-system                    nodelocaldns-8zvzk                                 1/1     Running            0             18m
kube-system                    openebs-localpv-provisioner-6f8b56f75-kbbmt        1/1     Running            0             18m
kube-system                    snapshot-controller-0                              1/1     Running            0             17m
kubesphere-controls-system     default-http-backend-56d9d4fdf7-j4b5v              1/1     Running            5 (13m ago)   16m
kubesphere-controls-system     kubectl-admin-7685cdd85b-fxvnp                     1/1     Running            0             13m
kubesphere-monitoring-system   alertmanager-main-0                                2/2     Running            0             14m
kubesphere-monitoring-system   kube-state-metrics-89f49579b-94kjr                 3/3     Running            0             14m
kubesphere-monitoring-system   node-exporter-7dmjc                                2/2     Running            0             14m
kubesphere-monitoring-system   notification-manager-deployment-6ff7974fbd-dcdxt   2/2     Running            0             14m
kubesphere-monitoring-system   notification-manager-operator-58bc989b46-dwnft     2/2     Running            0             14m
kubesphere-monitoring-system   prometheus-k8s-0                                   2/2     Running            0             14m
kubesphere-monitoring-system   prometheus-operator-fc9b55959-z97t7                2/2     Running            0             14m
kubesphere-system              ks-apiserver-5db774f4f-94cl6                       1/1     Running            0             16m
kubesphere-system              ks-console-64b56f967-lx9mh                         0/1     CrashLoopBackOff   8 (5s ago)    16m
kubesphere-system              ks-controller-manager-7b5f77b47f-q6c44             1/1     Running            0             16m
kubesphere-system              ks-installer-9b4c69688-6gtsx                       1/1     Running            0             18m

[root@node1 logs]# kubectl logs --tail 200 ks-console-64b56f967-lx9mh -n kubesphere-system

<--- Last few GCs --->


#
# Fatal process OOM in insufficient memory to create an Isolate
#


<--- JS stacktrace --->

Suggestion Does this project need to change the default node version? It seems that the problem is caused by the node version[1].Current node version is node:12-alpine3.14https://github.com/kubesphere/console/blob/09654378e9a5c5768b2646c1a401969a3c9e08b2/build/Dockerfile#L6. Ref

1. #1559