Determine changeset from build information

[imjasonh]

This updates knative.dev/pkg to @main to pick up a recent change to make
changeset.Get() determine the built version from information embedded in
the binary, and no longer return an error.

This also lets us remove symlinks for HEAD and refs in kodata, since
they were only there to enable the previous changeset.Get()
implementation.

#4928 recently bumped our knative/pkg dep to release-1.6 (which was the real hard part, thanks @vdemeester!). Here's the diff between release-1.6 and what we'll import now: knative/pkg@release-1.6...7b8b060

The relevant changes are knative/pkg#2548 and knative/pkg#2549

Similar change to knative/serving to drop HEAD and refs: knative/serving#13130

cc @dprotaso

/kind cleanup

Submitter Checklist

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

• Has Docs included if any changes are user facing
• 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)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Version informaiton added to workload labels is determined from information embedded by Go, instead of relying on symlinks to Git information in our build process.

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pod/pod.go	88.8%	89.3%	0.5
pkg/reconciler/taskrun/taskrun.go	80.3%	80.4%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pod/pod.go	88.8%	89.3%	0.5
pkg/reconciler/taskrun/taskrun.go	80.3%	80.4%	0.1

[imjasonh]

Oh, looks like tests still run with go 1.17:

go version go1.17.11 linux/amd64

We'll need to bump this to 1.18 to get this to work. Since Go only officially supports the last two versions, and 1.19 just came out, we should bump to 1.18 anyway.

[abayer]

/retest

[abayer]

...I forgot that #5134 hadn't merged yet. d'oh.

[abayer]

/retest

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pod/pod.go	88.8%	89.3%	0.5
pkg/reconciler/taskrun/taskrun.go	80.3%	80.4%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/pod/pod.go	88.8%	89.3%	0.5
pkg/reconciler/taskrun/taskrun.go	80.3%	80.4%	0.1

[abayer]

/test check-pr-has-kind-label

[tekton-robot]

@abayer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-tekton-pipeline-alpha-integration-tests
• /test pull-tekton-pipeline-build-tests
• /test pull-tekton-pipeline-integration-tests
• /test tekton-pipeline-unit-tests

The following commands are available to trigger optional jobs:

• /test pull-tekton-pipeline-go-coverage

Use /test all to run all jobs.

In response to this:

/test check-pr-has-kind-label

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/test-infra repository.

[abayer]

/approve

[vdemeester]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abayer, vdemeester

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,vdemeester]

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

[abayer]

/retest