Added CRD for resource export

[sbryzak]

Description

Introduce CRD for supporting user resource exports within member clusters.

Fixes https://issues.redhat.com/browse/CRT-1808

Checks

1. Did you run make generate target? yes

2. Did make generate change anything in other projects (host-operator, member-operator)? yes

3. In case of new CRD, did you the following? yes

   • make/generate.mk in this repository
   • resources/setup/roles/host.yaml in the sandbox-sre repository
   • PROJECT file: https://github.com/codeready-toolchain/host-operator/blob/master/PROJECT
   • CSV file: https://github.com/codeready-toolchain/host-operator/blob/master/config/manifests/bases/host-operator.clusterserviceversion.yaml

4. In case other projects are changed, please provides PR links.

   • member-operator: added generated files for export API type member-operator#455

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[MatousJobanek]

Thanks @sbryzak for this PR, but before doing anything in our code it would be cool to have:

• a document with a result of the GitOps primer code analysis
• defined gaps that we want to improve or change in the code
• proposal on how we want to proceed with the changes
• plan on how to integrate "our" API into the OpenShift console. Current OpenShift console is hard-coded to rely on the original GitOps primer API
• and mainly, conclusion & agreement on the team level

and btw - we stopped using the CRT project in Jira some time ago. Let's use SANDBOX 😉