Unify upgrader-sa config

[liangxia]

Unify upgrader-sa config by moving the config from each of the build farm clusters to common_except_app.ci.
This has the following effect,

• Add upgrader-sa config to build01
• Simply future maintenance work on upgrader-sa

$ find clusters/ -name upgrader-sa.yaml | sort
clusters/build-clusters/build02/upgrader-sa.yaml
clusters/build-clusters/build03/upgrader-sa.yaml
clusters/build-clusters/build04/upgrader-sa.yaml
clusters/build-clusters/build05/upgrader-sa.yaml
clusters/build-clusters/build06/upgrader-sa.yaml
clusters/build-clusters/build07/upgrader-sa.yaml
clusters/build-clusters/build08/upgrader-sa.yaml
clusters/build-clusters/build09/upgrader-sa.yaml
clusters/build-clusters/build10/upgrader-sa.yaml
clusters/build-clusters/build11/upgrader-sa.yaml
clusters/hosted-mgmt/upgrader-sa.yaml

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liangxia

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• clusters/OWNERS [liangxia]

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]

[REHEARSALNOTIFIER]
@liangxia: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci]

@liangxia: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[liangxia]

/cc @openshift/test-platform