Implement basic validation for Capact manifests

[pkosiec]

Description

Capact CLI [3SP]

capact validate for creating new manifests

1. Check if JSON schema in Types valid
   • Fix the JSON schemas if needed
2. Additional validation against Public Hub (enabled with an additional flag): [2SP]
   • Interface input + output: check typeRef + revision exists in Hub
   • Implementation: additionalInput.typeInstances : check typeRef + revision exists in Hub
   • Implements: check path + revision exists in Hub
   • Requires: check all requirements (path + revision) exist in Hub
   • Imports: check all methods from InterfaceGroups exist in Hub
   • Implementation + Type: check path + revision for every Attribute in metadata if exists in Hub
   • Validate all manifests and collect all errors
   • Update development guide

hub-manifests CI [1SP]

Spawn local Capact installation with CLI and run CLI manifests validation against existing Hub
- Reuse what we have on capactio/capact
- Idea: Populator should populate manifests from PR - disable populator in cluster, run populator locally

Subtasks

• Capact CLI - capact validate @pkosiec
• 4SP split to Engine validation for newly created action + validation for capact action create #425
• hub-manifests CI migration (dependency for the second subtask)

Reason

Validation is essential for creating new Capact manifests to avoid mistakes.

[pkosiec]

The following PRs are ready to review:

• Populate Type Attributes and require manifest revisions in OCF schema #436
• Implement concurrent manifest validation against Hub in CLI #437 [instruction how to run it inside]
• Fix manifest lint errors detected by CLI hub-manifests#16
• Update manifest validation command on CI pipelines hub-manifests#19

To do:

• Use it on CI