Add almost-empty v1 package

[lbernick]

Changes

This commit adds a package for v1 and updates the hack directory to generate
code and OpenAPI spec for v1. The v1 package is left as minimal as possible;
however, the code does not build and pass tests without at least one generated client.
Therefore, a Task type is added with only a Description field, with the rest of the
Task spec to be added in a future commit.

/kind misc

Submitter Checklist

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

• n/a Docs included if any changes are user facing
• n/a Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Release notes block below has been filled in
  (if there are no user facing changes, use release note "NONE")

Release Notes

NONE

[dibyom]

/retest

[lbernick]

/retest

[lbernick]

blocked on #5066

[lbernick]

/test pull-tekton-pipeline-alpha-integration-tests

[ywluogg]

/lgtm

[abayer]

Looks good in general, though I'm inherently a bit wary of adding a v1 api without it being fully populated. But it should be harmless, I guess?

Would like to get thoughts from others from @tektoncd/core-maintainers

[vdemeester]

Looks good in general, though I'm inherently a bit wary of adding a v1 api without it being fully populated. But it should be harmless, I guess?

Would like to get thoughts from others from @tektoncd/core-maintainers

@abayer this is just the code and the package, it is not exported or exposed in any way. This is what we did for v1beta1.
I think it's fine, except maybe the openapi/swagger generation 👼🏼

[abayer]

Looks good in general, though I'm inherently a bit wary of adding a v1 api without it being fully populated. But it should be harmless, I guess?
Would like to get thoughts from others from @tektoncd/core-maintainers

@abayer this is just the code and the package, it is not exported or exposed in any way. This is what we did for v1beta1. I think it's fine, except maybe the openapi/swagger generation 👼🏼

@lbernick handled that bit nicely - generating v1beta1 and v1 OpenAPI and swagger separately from each other. So given that, I think this is good to go. =)

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abayer

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 [abayer]

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

[lbernick]

/retest