add rulegroup definitions for different scopes

[junotx]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Define the following CRDs:

• RuleGroup: its instances take effect in its namespace
• ClusterRuleGroup: its instances take effect in its cluster
• GlobalRuleGroup: its instances take effect for all clusters

They will be used to provide easier alerting rule operations.

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Does this PR introduced a user-facing change?

Introduce CRDs to define alerting rules with defferent scopes for easier alerting rule operations

Additional documentation, usage docs, etc.:

[benjaminhuo]

/lgtm

[ks-ci-bot]

LGTM label has been added.

Git tree hash: ba359a1d595dcb283fcd5d19acb32b9732440b7c

[benjaminhuo]

/approve

[ks-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benjaminhuo, junotx

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:

• OWNERS [benjaminhuo]

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

[benjaminhuo]

/retest

[wansir]

/hold

The go version used in build-tools has been upgraded to 1.18.4, which will cause the ci job to fail.

[ks-ci-bot]

@junotx: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kubesphere-verify	91a525c	link	/test pull-kubesphere-verify
pull-kubesphere-unit-test	91a525c	link	/test pull-kubesphere-unit-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[benjaminhuo]

/hold

The go version used in build-tools has been upgraded to 1.18.4, which will cause the ci job to fail.

reverting go version to 1.17 for build-tools will fix this? @wansir