Discussion on how to trim down Tekton/Argo go pkg to resolve go.mod conflicts.

[Tomcli]

/kind feature

Description:
As part of contributing back KFP-Tekton V2 to upstream. One of the challenges is to resolve the go pkg conflicts between Argo and Tekton. In 2020, Argo and Tekton had many go-client conflicts in their pkg which is one of the reasons we have to separate the code base. Fast forward to today, Tekton still have the Knative dependency which conflicts with Argo's log and grpc-gateway packages. We want to see can we come up or rebuilt a new Tekton/Argo go pkg that can trim down from the original package because we only need the Tekton/Argo client to create the corresponding CRDs.

There are few options I have in mind:

1. Write our own Tekton/Argo go pkg that doesn't include unnecessary packages. However, we need to constantly sync and update our client package with the upstream Tekton/Argo project.
2. Contribute to both Tekton and Argo and create a small go client package similar to k8s.io/api. However, this requires us to get involve in multiple communities which we already see many challenges when contributing to the Tekton core API.

Any thoughts?

Additional information:
[Miscellaneous information that will assist in solving the issue.]

[Tomcli]

cc @yhwang @rimolive

[Tomcli]

related: tektoncd/pipeline#6483