move multicluster crds to the templates crds directory

[DanielXLee]

Signed-off-by: DanielXLee [email protected]

fixes: #39

[dixudx]

@DanielXLee I am not suggesting moving mcs crds into templates folder for below two reasons.

1. These mcs crds are not only used by clusternet-hub, but also for clusternet-agent. If we are putting them into template folder, we can not install clusternet-hub and clusternet-agent in a same cluster. Helm will complain the installation error. You have a try on this.
2. These mcs crds are mostly static and not updated with Clusternet. Helm will only help ensure CRDs in folder ./crds/ are installed. And helm will skip installing them when they are already installed.

We do move these crds into different folders back and forth. I think for non Clusternet crds, putting them into Helm default ./crds folder is not a bad choice.

cc @lmxia

[DanielXLee]

I didn't consider the case where the hub and agent are in the same cluster， it's more important.
If cannot install these crds when upgrading, I need manually install multicluster crds in these clusters, we have about 100 hub clusters. 😦

[dixudx]

If cannot install these crds when upgrading

These mcs crds are not changed. I did not get the upgrading issue here. @DanielXLee Could you elaborate what happens during the upgrading? Thanks.

I need manually install multicluster crds in these clusters, we have about 100 hub clusters.

Clusternet does have the capability to distribute resources to multiple clusters. These resources can be CRDs. This is not a blocking issue.