Upgrade cron-connector to fix panic

A panic made the cron-connector crash if the gateway
return an error or EOF during its invocation.

With faasd, this meant the connector stayed in an exited state
with Kubernetes, it would have restarted, however it's always
better if there is no panic, and the code can recover
gracefully.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

Author: alexellis

chart/cron-connector/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 description: Trigger OpenFaaS Functions with cron schedules
 name: cron-connector
-version: 0.6.11
+version: 0.6.12
 sources:
 - https://github.com/openfaas/cron-connector
 home: https://www.openfaas.com

chart/cron-connector/values.yaml

@@ -1,9 +1,9 @@
 openfaasPro: false
 
 pro:
-  image: ghcr.io/openfaasltd/cron-connector:0.2.8
+  image: ghcr.io/openfaasltd/cron-connector:0.2.9
 
-image: ghcr.io/openfaas/cron-connector:0.6.1
+image: ghcr.io/openfaas/cron-connector:0.7.0
 
 logs:
   # Log debug messages