OCPQE-30671:Add [OTP] to migrated tests-private cases Per ERT

[kuiwang02]

Add [OTP] Tags to Migrated Tests-Private Test Cases

Why / Problem Statement

The ERT team requires all OLMv1 test cases migrated from openshift-tests-private to be tagged with [OTP] labels for proper test categorization and execution. Additionally, the OTE framework requires original-name Ginkgo labels when renaming tests to maintain test history tracking.

What / Solution

This PR adds [OTP] tags to all OLMv1 migrated test case titles and implements proper test name tracking via original-name labels as required by the OTE framework.

Key Points:

• [OTP] tag inserted immediately after PolarionID
• Please follow README to keep test name unique.

Note:
1, LEVEL0 ginkgo label change to title label [Level0]
2, Please Do not use &|!,()/ in case title for possible ginkgo label.

Assisted-by: Claude Code

/cc @jianzhangbjz @Xia-Zhao-rh @bandrade

[openshift-ci-robot]

@kuiwang02: This pull request references OCPQE-30671 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

Add [OTP] Tags to Migrated Tests-Private Test Cases

Why / Problem Statement

The ERT team requires all OLMv1 test cases migrated from openshift-tests-private to be tagged with [OTP] labels for proper test categorization and execution. Additionally, the OTE framework requires original-name Ginkgo labels when renaming tests to maintain test history tracking.

What / Solution

This PR adds [OTP] tags to all OLMv1 migrated test case titles and implements proper test name tracking via original-name labels as required by the OTE framework.

Key Points:

• [OTP] tag inserted immediately after PolarionID
• Please follow README to keep test name unique.

Note:
1, LEVEL0 ginkgo label change to title label [Level0]
2, Please Do not use &|!,()/ in case title for possible ginkgo label.

Assisted-by: Claude Code

/cc @jianzhangbjz @Xia-Zhao-rh @bandrade

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@kuiwang02: all tests passed!

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.

[jianzhangbjz]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz, kuiwang02

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

The pull request process is described here

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS [jianzhangbjz]

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

[kuiwang02]

/verified by @kuiwang02

[openshift-ci-robot]

@kuiwang02: This PR has been marked as verified by @kuiwang02.

In response to this:

/verified by @kuiwang02

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 openshift-eng/jira-lifecycle-plugin repository.