Refactor TaskRuns out of BuildRun Controller

[adambkaplan]

Changes

Initial effort to abstract concrete usage of Tekton TaskRuns out of the BuildRun controller. This includes the creation of new a new interface (ImageBuildRunner), factories for converting TaskRuns to ImageBuildRunners, and updates to controller code.

/kind cleanup

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

[adambkaplan]

This is a "take two" of my attempt to refactor TaskRuns out of the BuildRun contrller (see #1866). This time I am narrowing the scope a bit and using AI assistance.

[adambkaplan]

Taking WIP off this PR (hopefully the full suite passes 🤞 )

[dorzel]

@adambkaplan Is the eventual aim to have TaskRuns be a completely "optional" or modular component to Shipwright, such that if another imagebuildrunner (in this framework) were to come along that can implement the interfaces in this PR, it would use that instead?

[adambkaplan]

@adambkaplan Is the eventual aim to have TaskRuns be a completely "optional" or modular component to Shipwright, such that if another imagebuildrunner (in this framework) were to come along that can implement the interfaces in this PR, it would use that instead?

More the "modular" idea. For multi-arch image builds, orchestrating with a PipelineRun is needed to run parallel builds on native infrastructure/nodes. We have also discussed a distant future state where Shipwright could orchestrate other Kubernetes workload types, such as Jobs or Argo Workflows. This PR would be the first of many baby steps down that path.

[dorzel]

This seems like a good first step to me given what the intended scope currently is. ImageBuildRunner seems like a reasonable interface and I would expect it would get more generic over time as additional implementations come in.

[SaschaSchwarze0]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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:

• OWNERS [SaschaSchwarze0]

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