[FluxCD Integration] Add independent UI components for FluxCD Application lifecycle management

### Motivation
FluxCD is similar to ArgoCD but not same.
Some concepts in ArgoCD like SyncPolicy and SyncOptions are not exist in FluxCD. Some concepts in FluxCD like more Helm Parameters, Template and Multi-Clusters are not exist in ArgoCD. Mix ArgoCD and FluxCD together may causes tight coupling.

### Implement
- Add Separate UI components such as `src/components/Forms/FluxCD/BaseInfo` and `src/components/Forms/FluxCD/Advance`.
- Send requests to `.../namespace/{namespace}/fluxcd/applications` apis to interacte with ks-apiserver.
- Keep the same UI/UX in most space like source and destination.
- Choose the two Separate UI by ClusterConfiguration settings as following

/area console