Dynamic resources files JSON schema file structure

[Adam0Brien]

PR Template:

Describe your changes

Proposed design for storing and validating JSON schemas/payloads

• The validation will take the respective schemas and validate resources/reporters based on the file names/directories in this setup
• In this example k8s_cluster.json defines the required fields of a resource_type
• Reporterdata will then be validated seperatly after the resource data

 └── resources
│       ├── k8s_cluster
│       │   ├── config.yaml # Defines what reporters can be associated with a resource
│       │   ├── k8s_cluster.json # resource type schema
│       │   └── reporters
│       │       ├── acm
│       │       │   ├── acm.json # reporter type JSON schema
│       │       │   ├── config.yaml # define relation properties/namespace
│       │       │  
│       │       └── ocm
│       │           ├── config.yaml # define relation properties/namespace
│       │           └── ocm.json # reporter type JSON schema

Ticket reference (if applicable)

Fixes #https://issues.redhat.com/browse/RHCLOUD-37415

Checklist

• Are the agreed upon acceptance criteria fulfilled?

• Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

• Do your changes have passing automated tests and sufficient observability?

• Are the work steps you introduced repeatable by others, either through automation or documentation?

  • If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
  • An SOP (Standard Operating Procedure) was created

• The Changes were automatically built, tested, and - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

• Are the agreed upon coding/architectural practices applied?

• Are security needs fullfilled? (e.g. no internal URL)

• Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

• For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

[akoserwal]

We can add major/minor version on the config?
@jmelis

[akoserwal]

Looks good to me. Left comment to discuss adding versioning

[app-sre-bot]

Can one of the admins verify this patch?