OCPCLOUD-2642: Add azure-service-operator jobs and config to openshift-priv

[nrb]

Entries were copied from https://github.com/openshift/release/tree/master/ci-operator/config/openshift/azure-service-operator and https://github.com/openshift/release/tree/master/ci-operator/jobs/openshift/azure-service-operator and the orgs were updated.

[openshift-ci-robot]

@nrb: This pull request references OCPCLOUD-2642 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 story to target the "4.18.0" version, but no target version was set.

In response to this:

Entries were copied from https://github.com/openshift/release/tree/master/ci-operator/config/openshift/azure-service-operator and https://github.com/openshift/release/tree/master/ci-operator/jobs/openshift/azure-service-operator and the orgs were updated.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

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:

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

[openshift-ci-robot]

@nrb, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load Prow configuration from release repo: [duplicated basename is not allowed: openshift-azure-service-operator-main-postsubmits.yaml, duplicated basename is not allowed: openshift-azure-service-operator-main-presubmits.yaml]

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@nrb: The following tests 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/prow-config-semantics	aae6d15	link	true	/test prow-config-semantics
ci/prow/generated-config	aae6d15	link	true	/test generated-config
ci/prow/check-gh-automation	aae6d15	link	true	/test check-gh-automation
ci/prow/prow-config-filenames	aae6d15	link	true	/test prow-config-filenames
ci/prow/config	aae6d15	link	true	/test config
ci/prow/ci-operator-config	aae6d15	link	true	/test ci-operator-config
ci/prow/ci-operator-config-metadata	aae6d15	link	true	/test ci-operator-config-metadata

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.