Is your feature request related to a problem? Please describe.
When enabling kube-explorer in autok3s-ui for cluster, it will start kube-explorer with localhost and random port. While kube-explorer supports listen request on sock, autok3s can start kube-explorer via socket and proxy request to kube-explorer via sock also.
Also kube-explorer handles html modification itself, autok3s doesn't need to do that anymore.
Describe the solution you'd like
Start kube-explorer with socket and proxy request to socket.
Describe alternatives you've considered
N/A
Additional context
N/A