sysbox rewrite `entrypoint.sh` but not suport `<` in kubelet external args

issue

kubelet start failed after sysbox install.
error msg:

kubelet --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-node.yaml --eviction-hard=memory.available<10Mi,imagefs.available<1%,nodefs.available<1%,nodefs.inodesFree<1% 
/opt/rke-tools/entrypoint.sh: line 110: 10Mi,imagefs.available: No such file or directory

context

rancher: 2.6.8
k8s: 1.22.16
docker: 19.03.15

the exec command in entrypoint.sh( sysbox rewrote)

exec kubelet --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-node.yaml --read-only-port=0 --cluster-domain=cluster.local --cgroups-per-qos=True --enforce-node-allocatable=pods --eviction-hard=memory.available<10Mi,imagefs.available<1%,nodefs.available<1%,nodefs.inodesFree<1% --resolv-conf=/etc/resolv.conf --event-qps=0 --volume-plugin-dir=/var/lib/kubelet/volumeplugins --pod-infra-container-image=rancher/mirrored-pause:3.6 --anonymous-auth=false --cni-conf-dir=/etc/cni/net.d --fail-swap-on=false --network-plugin=cni --v=2  --system-reserved=cpu=10m,memory=10Mi,ephemeral-storage=100Mi,pid=10000 --cgroup-driver=cgroupfs --resolv-conf=/run/systemd/resolve/resolv.conf --container-runtime=remote --container-runtime-endpoint=unix:///var/run/crio/crio.sock --image-service-endpoint=unix:///var/run/crio/crio.sock --runtime-cgroups=/system.slice/crio.service --runtime-request-timeout=6m

and after hardcode change entrypoint.sh. when we change kubelet external args, it will not work.