UPSTREAM: <carry>: OTE extension should store repo source

[stbenjam]

OTE has ability to store the URL for the git repository, but we're not currently setting it.

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR is related to:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[openshift-ci-robot]

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 7406f26|UPSTREAM: : OTE extension should store repo source: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stbenjam
Once this PR has been reviewed and has the lgtm label, please assign p0lyn0mial for approval. For more information see the 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:

• DOWNSTREAM_OWNERS

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

[openshift-ci]

@stbenjam: 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/e2e-aws-ovn-hypershift	7406f26	link	true	/test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-ovn-crun	7406f26	link	true	/test e2e-aws-ovn-crun
ci/prow/e2e-aws-ovn-cgroupsv2	7406f26	link	true	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-crun-wasm	7406f26	link	true	/test e2e-aws-crun-wasm
ci/prow/e2e-gcp	7406f26	link	true	/test e2e-gcp

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.