Fixing issues for the configMap configuration

[neumanndaniel]

This PR fixes a couple of issues resulting in a Provider failed state of the customer container module, when the following scenarios are met for the configMap configuration.

Scenario	Current IoT Edge VK provider version	New IoT Edge VK provider version
Missing configMap	Pod running	Pod running
Missing data part in configMap	Provider failed	Pod running
Empty data part in configMap	Provider failed	Pod running
Missing restartPolicy part in configMap	Provider failed	Pod running
Empty restartPolicy part in configMap	Provider failed	Pod running
Missing createOptions part in configMap	Provider failed	Pod running

Example configMaps for each scenario except the first one

Missing data part in configMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: go-webapp-arm

Empty data part in configMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: go-webapp-arm
data:

Missing restartPolicy part in configMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: go-webapp-arm
data:
  status: running
  version: "1.0"
  createOptions: |
    {
      "HostConfig": {
        "PortBindings": {
          "8080/tcp": [
            {
              "HostPort": "80"
            }
          ]
        }
      }
    }

Empty restartPolicy part in configMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: go-webapp-arm
data:
  status: running
  restartPolicy:

With an empty restaryPolicy part you need to run kubectl apply -f deployment.yaml --validate=false to execute the deployment process.

Missing createOptions part in configMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: go-webapp-arm
data:
  status: running
  restartPolicy: always
  version: "1.0"

[neumanndaniel]

Ping @veyalla @avranju

[neumanndaniel]

@avranju Side note @veyalla needs to build a new container image and push it to https://hub.docker.com/r/microsoft/iot-edge-vk-provider/tags/