User specified public key is not set with Arktos VM

[yb01]

This is related with issue #1316

What happened:

User should be able to set the public key in Pod def and use the private key to access VM. Arktos VM runtime didn't get this set at the VM.

this is done through the cloud-init process internally during the VM creation and the cloud-init user data didn't set and hence the public Key is not set at the VM.

== runtime got the public key correctly from Arktos:

2022-02-01T00:15:17.419566548Z stderr F I0201 00:15:17.419436  199663 grpc.go:110] ENTER: /runtime.v1alpha2.RuntimeService/RunPodSandbox():
2022-02-01T00:15:17.419583237Z stderr F config:
2022-02-01T00:15:17.419590131Z stderr F   annotations:
2022-02-01T00:15:17.419597554Z stderr F     VirtletCPUModel: host-model
2022-02-01T00:15:17.419603076Z stderr F     VirtletRootVolumeSize: 4Gi
2022-02-01T00:15:17.419609182Z stderr F     VirtletSSHKeys: |
2022-02-01T00:15:17.419621661Z stderr F       ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCaJEcFDXEK2ZbX0ZLS1EIYFZRbDAcRfuVjpstSc0De8+sV1aiu+dePxdkuDRwqFtCyk6dEZkssjOkBXtri00MECLkir6FcH3kKOJtbJ6vy3uaJc9w1ERo+wyl6SkAh/+JTJkp7QRXj8oylW5E20LsbnA/dIwWzAF51PPwF7A7FtNg9DnwPqMkxFo1Th/buOMKbP5ZA1mmNNtmzbMpMfJATvVyiv3ccsSJKOiyQr6UG+j7sc/7jMVz5Xk34Vd0l8GwcB0334MchHckmqDB142h/NCWTr8oLakDNvkfC1YneAfAO41hDkUbxPtVBG5M/o7P4fxoqiHEX+ZLfRxDtHB53 me@localhost
2022-02-01T00:15:17.419629554Z stderr F     VirtletVCPUCount: "1"
2022-02-01T00:15:17.41963531Z stderr F     kubernetes.io/config.seen: 2022-02-01T00:15:17.391051604Z
2022-02-01T00:15:17.419640906Z stderr F     kubernetes.io/config.source: api0
2022-02-01T00:15:17.419647005Z stderr F     kubernetes.io/target-runtime: virtlet.cloud
2022-02-01T00:15:17.419653248Z stderr F   dns_config:
2022-02-01T00:15:17.419658682Z stderr F     options:
2022-02-01T00:15:17.419663848Z stderr F     - ndots:5
2022-02-01T00:15:17.419668692Z stderr F     searches:
2022-02-01T00:15:17.419673965Z stderr F     - kube-system.svc.cluster.local
2022-02-01T00:15:17.419679292Z stderr F     - svc.cluster.local
2022-02-01T00:15:17.419684576Z stderr F     - cluster.local
2022-02-01T00:15:17.41968987Z stderr F     - us-west-2.compute.internal
2022-02-01T00:15:17.419713111Z stderr F     servers:
2022-02-01T00:15:17.419718841Z stderr F     - 10.0.0.141
2022-02-01T00:15:17.419723845Z stderr F   hostname: vmdefault
2022-02-01T00:15:17.419729053Z stderr F   labels:
2022-02-01T00:15:17.419734362Z stderr F     io.kubernetes.pod.name: vmdefault
2022-02-01T00:15:17.419740296Z stderr F     io.kubernetes.pod.namespace: kube-system
2022-02-01T00:15:17.419745597Z stderr F     io.kubernetes.pod.tenant: system
2022-02-01T00:15:17.419751427Z stderr F     io.kubernetes.pod.uid: a2faac73-9ae1-42e1-bf16-f524ee91f1a7

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?: