Optimize installation flow

[lfbear]

What would you like to be added:

1. Split installation script for different purposes, in a stand-alone cluster(for production) or a kind cluster(for development)
2. No logger using export diff KUBECONFIG to switch multi-clusters in the install script

Why is this needed:

1. Likes do not use Kind to install karmada #303, the newcomers may not have a sense for kind when they wanna make a production installation, so we should make it clear in the installation stage
2. Using a native way to switch multi-clusters for kubectl

[lfbear]

If it's ok, assign to me

[RainbowMango]

Split installation script for different purposes, in a stand-alone cluster(for production)

I'm really looking forward to it. I've been asked many times.

[pigletfly]

Can we support install via Helm? @lfbear Are you planning to do this ?

[lfbear]

Can we support install via Helm? @lfbear Are you planning to do this ?

That's a good idea, but I have no plan for this version. I need to make the installation stage clear fisrtly.

[pigletfly]

Can we use https://github.com/jetstack/cert-manager for caBundle injection ?