Support `ClusterTriggerBinding` for on-premise BitBucket Server

1. Proposed title of this feature request

  Support `ClusterTriggerBinding` for on-premise BitBucket Server

2. What is the nature and description of the request?

  When testing a POST Webhooks from BitBucket to OCP using the built-in bitbucket-push ClusterTriggerBinding, the following payload fields do not match error is thrown:

{"level":"error","ts":"2022-02-10T09:02:20.826Z","logger":"eventlistener","caller":"sink/sink.go:232","msg":"failed to ApplyEventValuesToParams: failed to replace JSONPath value for param git-revision: $(body.changes[0].ref.displayId): changes is not found","knative.dev/controller":"eventlistener","/triggers-eventid":"cae44871-4fa7-42b5-b4d3-baf4ec9d87b7","/trigger":"","stacktrace":"github.com/tektoncd/triggers/pkg/sink.Sink.processTrigger\n\t/opt/app-root/src/go/src/github.com/tektoncd/triggers/pkg/sink/sink.go:232\ngithub.com/tektoncd/triggers/pkg/sink.Sink.HandleEvent.func1\n\t/opt/app-root/src/go/src/github.com/tektoncd/triggers/pkg/sink/sink.go:127"} 

  Bug SRVKP-2082 was opened to report this issue.

  Currently the operator only ship `ClusterTriggerBinding` for the public instance of Bitbucket.

  The aim of this RFE is to also support `ClusterTriggerBinding` for on-premise BitBucket Server.

3. Why does the customer need this? (List the business requirements here)

  Integration with on-premise BitBucket Server.

4. List any affected packages or components.

  OpenShift Pipelines