e2e-test provisioner should report installed operator revisions

[mkulke]

Describe the bug

Operator installations are dynamic, since we use main in versions.yaml for the coco-operator as ref, and the operator will install different kata runtime payloads on the node, depending on when the provisioner is being executed.

This is unfortunate if there's is a change in the runtime that breaks CAA, because it's hard to figure out which change caused the breakage.

A potential fix would be to add some simple log statement to show the exact runtime that was deployed by the operator, think:

k describe po cc-operator-daemon-install-t92cd -n confidential-containers-system | grep Image
    Image:         quay.io/kata-containers/kata-deploy-ci:kata-containers-e4c023a9fa1aee82e5e575470c005cf7a30a6555-amd64
    Image ID:      quay.io/kata-containers/kata-deploy-ci@sha256:d6bd2f677f39f2b8afa065c110c02c9867a7e4fa892205f393a6ea1272e19f2b

How to reproduce

n/a

CoCo version information

n/a

What TEE are you seeing the problem on

AzSnpVtpm

Failing command and relevant log output

n/a