spilt karmada-config ConfigMap in helm chart and split crd yaml into group files

[XiShanYongYe-Chang]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

In order to fix the issue: #3713

Which issue(s) this PR fixes:
Fixes #3713

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[XiShanYongYe-Chang]

/cc @Poor12 @RainbowMango

[codecov-commenter]

Codecov Report

Merging #3721 (fad05ce) into master (b005d5b) will increase coverage by 0.00%.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##           master    #3721   +/-   ##
=======================================
  Coverage   55.68%   55.69%           
=======================================
  Files         222      222           
  Lines       21195    21195           
=======================================
+ Hits        11803    11805    +2     
+ Misses       8765     8763    -2     
  Partials      627      627           

Flag	Coverage Δ
unittests	55.69% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

[Poor12]

/lgtm

[RainbowMango]

/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• charts/OWNERS [RainbowMango]
• hack/OWNERS [RainbowMango]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[RainbowMango]

I just realized that karmadactl init is using the crd files, please help to confirm it still works with this change.