feat(RHOAIENG-15495): Add component metadata manifest

[ruivieira]

Refer to RHOAIENG-15495

Add template component_metadata to be populated with release values when performing community releases.

[github-actions]

PR image build and manifest generation completed successfully!

📦 PR image: quay.io/trustyai/trustyai-service-operator-ci:a2f17d651f75504f6fb901849109e1c91058cd34

📦 LMES driver image: quay.io/trustyai/ta-lmes-driver:a2f17d651f75504f6fb901849109e1c91058cd34

📦 LMES job image: quay.io/trustyai/ta-lmes-job:a2f17d651f75504f6fb901849109e1c91058cd34

🗂️ CI manifests

devFlags:
  manifests:
    - contextDir: config
      sourcePath: ''
      uri: https://api.github.com/repos/trustyai-explainability/trustyai-service-operator-ci/tarball/operator-a2f17d651f75504f6fb901849109e1c91058cd34

[openshift-ci]

@ruivieira: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/trustyai-service-operator-e2e	a2f17d6	link	true	/test trustyai-service-operator-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[danielezonca]

to be populated with release values when performing community releases

Do you plan to make this automatic?

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: danielezonca, RobGeada

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

[ruivieira]

to be populated with release values when performing community releases

Do you plan to make this automatic?

@danielezonca I could include some automation in a future PR. Perhaps getting the values from the release branch name? I think it's better than tag-based, since in that case the changes would happen after the tag is pushed.