remove liveness checks on pebble deployments in e2e tests

liveness checks are a feature in kubernetes meant to restart hung
workloads. Since pebble stores account information in-memory, failing
a liveness check means that any running test will fail.

Because we're using pebble as part of a testsuite, we're protected
against hangs by the test just timing out.

On resource constrained environments (like my laptop), I've seen
the liveness check fail during startup, causing reboot loops and
timeouts. Since rebooting pebble mid-test will cause tests to fail
anyhow, we should probably disable this check.

Signed-off-by: Daniel Morsing <dmo@jetstack.io>

test/e2e/charts/pebble/templates/deployment.yaml

@@ -26,13 +26,6 @@ spec:
             periodSeconds: 1
             failureThreshold: 10
             successThreshold: 1
-          livenessProbe:
-            tcpSocket:
-              port: 14000
-            initialDelaySeconds: 1
-            periodSeconds: 1
-            failureThreshold: 10
-            successThreshold: 1
           resources:
 {{ toYaml .Values.resources | indent 12 }}
     {{- if .Values.nodeSelector }}