Add InterceptorType as a cluster scoped CRD for registering interceptors

This commit adds a new CRD type called InterceptorType. In TEP-0026 this
type was called InterceptorConfig though InterceptorType sounds a bit
clearer.

The `spec` currently only contains a clientConfig field to locate where
the interceptor is running. Other fields will be added as they are
implemented in follow ups.

This commit also adds a simple reconciler for this type that resolves
the clientConfig to a URL and adds it to the `status.address.url` field.

Part of tektoncd#868

Signed-off-by: Dibyo Mukherjee <[email protected]>

examples/rbac.yaml

@@ -10,7 +10,7 @@ metadata:
 rules:
 # EventListeners need to be able to fetch all namespaced resources
 - apiGroups: ["triggers.tekton.dev"]
-  resources: ["eventlisteners", "triggerbindings", "triggertemplates", "triggers"]
+  resources: ["eventlisteners",  "triggerbindings", "triggertemplates", "triggers"]
   verbs: ["get", "list", "watch"]
 - apiGroups: [""]
  # configmaps is needed for updating logging config

pkg/apis/triggers/v1alpha1/interceptor_type_defaults_test.go

@@ -1,12 +1,12 @@
 package v1alpha1_test
 
 import (
-	"context"
-	"testing"
-
 	"github.com/google/go-cmp/cmp"
 	triggersv1 "github.com/tektoncd/triggers/pkg/apis/triggers/v1alpha1"
 	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
+
+	"context"
+	"testing"
 )
 
 func TestInterceptorTypeSetDefaults(t *testing.T) {