[Submission Pipeline] Create new submission workflow for modulectl

[ruanxin]

Description

We need to design and implement a new submission pipeline dedicated specifically to the modulectl tool. This pipeline should be isolated from the existing pipelines to ensure that changes related to modulectl do not affect the current submission processes.

Requirements:

Based on existing submission-workflow.yaml, we will need to modify or implement the following Azure DevOps pipeline steps:

• Determine Action:
  • This action should detect module manifest based on the new folder structure .
  • [Submission Pipeline] New Determine Action for Version-Based Module Manifests #12670
• Collect module info:
  • This action should based on new module-config.yaml structure
  • [Submission Pipeline] New Collect module info action triggered by version based module manifests #12671
• check module name and version
  • The existing one is channel based, concaticated by several validation steps as a template check-module-name-and-version.yaml, create new template based on new folder structure
  • [Submission Pipeline] New module validation template #12672
• replace Download Kyma cli with download modulectl
  • [Submission Pipeline] Create download-modulectl script and reference it in the workflow modulectl#153
• Validate module changes
  • using modulectl dry run create instead of kyma-alpha-create-module.sh
  • [Submission Pipeline] Create modulectl-create script and reference it in the workflow modulectl#154
• Create Module
  • using modulectl create instead of kyma-alpha-create-module.sh
  • [Submission Pipeline] Create modulectl-create script and reference it in the workflow modulectl#154
• Update Kustomization.yaml if needed
• ❓ new kyma modules might not necessary using kustomization.yaml
• [Submission Pipeline] Adapt the Kustomization.yaml to the new ModuleTemplates #12674

❗ All the steps not mentioned mostly just need to follow the current pipeline structure, but must be verified accordlying. If certain steps script can't be reused, create new one instead of modifing existing one.

Acceptance Criteria

• A new submission pipeline is implemented that triggered by updates in module-manifests repo with new folder structures and generates new ModuleTemplate as well as ModuleReleaseMeta in kyma-modules repo.

[LeelaChacha]

We use the feature/new-submission-pipeline branch in the kyma/test-infra repo. We will implement all the features there and merge to main when ready.