Consider passing non-user configurable properties into vAppConfig

[zyiyi11]

We have a user trying to use Nested ESXi OVA, which includes one hidden property (used for debugging purposes), but it had no value set after deployed. The only way to resolve this right now was to import the OVA into vSphere, change the hidden property to configurable AND then specify that in vAppConfig spec and VM Service was able to power it on.

For basic OVF/OVA, this is not an issue but for more complex ones that leverage hidden properties. other VMware appliances like VCSA also uses hidden properties for various reasons

Please describe the solution you would like. Right now, any non user configurable properties are ignored. We can consider passing these into vAppConfig. ref: https://github.com/vmware-tanzu/vm-operator/blob/8f2552faf4dce6a44d6c50d2c72163034d25796d/pkg/vmprovider/providers/vsphere/session/session_util.go#L52-L55

Is there anything else you would like to add?

Please tell us about your environment.

	Value	How to Obtain
Supervisor version		rpm -qa VMware-wcp on the vCenter appliance
Supervisor node image version		rpm -qa VMware-wcpovf on the vCenter appliance
Kubernetes version		kubectl version
VM Operator version		kubectl -n vmware-system-vmop get pods \ -ojsonpath='{range .items[*].spec.containers[*]}{.image}{"\n"}{end}' | \ sort -u | \ grep vmop | \ awk -F'/' '{print $3}' | \ awk -F: '{print $2}'