Feat: Add metadata validation workflow and scripts

[alyssacgoins]

Add script validate_metadata.py to the scripts directory. Validates metadata schema with the formatting below, and includes a Github Actions workflow.

tier: core | third_party
name: <string>
stability: alpha | beta | stable
dependencies:
  kubeflow:
    - name: Pipelines  # Kubeflow Pipelines version is required
      version: '>=2.5'
    - name: Trainer  # Other official Kubeflow components required. This is a validated list enforced by CI.
      version: '>=2.0'
  external_services:  # A free form of external service dependencies
    - name: Argo Workflows
      version: "3.6"
tags:  # Optional and may be used for tooling built around the catalog in the future
  - training
  - evaluation
lastVerified: 2025-03-15T00:00:00Z
ci:
  skip_dependency_probe: false
  pytest: optional
links:
  documentation: https://kubeflow.org/components/<name>
  issue_tracker: https://github.com/kubeflow/kfp-components/issues

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from humairak. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[VaniHaripriya]

Suggested change

	python "${{ env.VALIDATION_SCRIPT_PATH }}" --item $FILE_PATH
	python "${{ env.VALIDATION_SCRIPT_PATH }}" --component $FILE_PATH

I see that the validate_metadata.py script accepts --component flag.

[alyssacgoins]

Updated this argument to --dir

[google-oss-prow]

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubeflow org. You can then trigger verification by writing /verify-owners in a comment.

• sample-approver
  • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
  • scripts/validate_metadata/test_data/directories_metadata/valid/OWNERS