Revert "e2e/test.sh: VenafiConnection CRDs weren't being installed"

The error that I was trying to fix was:

 failed to list *v1alpha1.VenafiConnection: venaficonnections.jetstack.io
 is forbidden: User "system:serviceaccount:venafi:venafi-connection"
 cannot list resource "venaficonnections" in API group "jetstack.io" at
 the cluster scope

I then added crds.venafiConnection.include=true, thinking that the
agent's helm chart wasn't installing the RBAC.

But I found that ./hack/e2e/test.sh was installing venafi enhanced
issuer along with the Agent, which means the venafi-connection helm
chart was being installed and so crds.venafiConnection.include=true
isn't needed.

Author: maelvls

hack/e2e/values.venafi-kubernetes-agent.yaml

@@ -6,7 +6,3 @@ config:
 authentication:
   venafiConnection:
     enabled: true
-
-crds:
-  venafiConnection:
-    include: true