fix: resolve issue where resolutionrequest defaulted to v1alpha1 vs v1beta1

[aaron-prindle]

/kind cleanup

Changes

It was identified that the default APIVersion was v1alpha1 in pkg/apis/resolution/v1beta1/resolution_request_defaults.go when it should be v1beta1. This PR fixes this incorrect default API version

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• [N/A] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• [N/A] Has Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Resolved issue where resolutionrequest defaulted to v1alpha1 when it should be v1beta1

[jerop]

/kind bug

[jerop]

Thanks for the quick fix @aaron-prindle!

I was wondering if we even need this defaulting, because how is the object a ResolutionRequest if the APIVersion and Kind is not set? The defaulting we have on the other CRDs is on the Spec and Status, not on the APIVersion and Kind of the object itself. Maybe this is why this issue has not been caught in the 1yr+ since v1betat1.ResolutionRequest was released. I wonder if it'd better to remove this defaulting, or whether I'm missing something obvious.

cc @tektoncd/core-maintainers

[dibyom]

Thanks for the fix!

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

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:

• pkg/apis/OWNERS [dibyom]

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

[jerop]

recorded my questions in #7447 to unblock this fix

thanks @aaron-prindle

/lgtm