Add optional Shipwright Triggers deployment support

[IrvingMg]

Changes

Add optional Shipwright Triggers deployment support via spec.triggers.enable on the ShipwrightBuild CR.

• Introduce a new TriggersSpec field and pkg/triggers package
• Upgrade the TektonConfig profile from "lite" to "base" when enabled
• Perform cleanup on disable or CR deletion
• Add RBAC for triggers resources and Tekton API permissions

Related Issue

Fixes #240

Type of PR

/kind feature

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Kind label has been set
• 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

Add optional Shipwright Triggers support. Set `spec.triggers.enable: true` on the ShipwrightBuild CR to deploy the Triggers controller alongside Shipwright Build.

[IrvingMg]

@shipwright-io/contributors PTAL

[adambkaplan]

/approve

Marking "approve" to indicate this is a feature we want to include in the next release.

I have a few comments around the API and how we manage RBAC, plus an additional test scenario to consider. Otherwise this is a really solid PR - thanks @IrvingMg for the contribution!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

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:

• OWNERS [adambkaplan]

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