kcctl registry optimization

[lixd]

Describe the Bug
A clear and concise description of what the bug is.
kcctl registry Parameter is too more，maybe we can save it in a config file.
like this，list repository from registry,we need specify --node flag

kcctl registry list --node xxx --type repository,

we can save node info to a config file,when we deploy it，and in latest op we can omit --node flag,and read it from config file first.

and --type flag maybe set a defaut value as repository, so that we can list by this command:

kcctl registry list

and more others optimization

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

Versions Used
Kubernetes: 1.27.4
Kubeclipper: 1.4.1

Environment
How many nodes and their hardware configuration:

For example: CentOS 7.5 / 3 masters: 8cpu/8g; 3 nodes: 8cpu/16g
(and other info are welcomed to help us debugging)

How To Reproduce
Steps to reproduce the behavior:

1. kcctl registry deploy，deploy registry
2. kcctl registry list --node xxx --type repository,list images in registry
   Expected behavior
   A clear and concise description of what you expected to happen.