chore: rename Go module path from openshift-pipelines to tektoncd

[chmouel]

Context

The Go module path currently uses the openshift-pipelines org. It must be renamed to tektoncd as part of the migration. This is a breaking change for any downstream consumers importing the PAC module.

Files to update

• go.mod:1: github.com/openshift-pipelines/pipelines-as-code → github.com/tektoncd/pipelines-as-code
• docs/go.mod:1: same rename
• Makefile:34: two -ldflags occurrences referencing the old module path (version + settings packages)
• config/400-controller.yaml:48: ko://github.com/openshift-pipelines/pipelines-as-code/cmd/pipelines-as-code-controller
• config/500-watcher.yaml:48: ko://github.com/openshift-pipelines/pipelines-as-code/cmd/pipelines-as-code-watcher
• config/600-webhook.yaml:47: ko://github.com/openshift-pipelines/pipelines-as-code/cmd/pipelines-as-code-webhook
• pkg/test/nonoai/deployment.yaml: ko:// paths referencing old module
• All Go import paths in pkg/, cmd/, test/, internal/ — mass replace

Steps

1. Run: find . -type f -name '*.go' | xargs sed -i 's|github.com/openshift-pipelines/pipelines-as-code|github.com/tektoncd/pipelines-as-code|g'
2. Update go.mod, docs/go.mod, Makefile, and YAML config files as listed above
3. Run make vendor && make test to verify

Notes

• This is a breaking change for downstream consumers importing the Go module directly.
• The GitHub repo transfer (when it happens) will make the old import path a redirect, but Go modules are pinned by path — downstream users must update their go.mod.