Fix bug in UVM activation when using OCI Windows.Resources.Memory.Limit
Fix bug in UVM activation when using OCI Windows.Resources.Memory.Limit

When using the sandbox override annotation:
"io.microsoft.virtualmachine.computetopology.memory.sizeinmb" in CRI the
setting is expected in MB. When using OCI Windows.Resources.Memory.Limit the
setting is expeced in Bytes. The platform expects the setting in MB. So the
resolver now ALWAYS returns MB regardless if using the annotation override or
OCI spec.

Signed-off-by: Justin Terry (VM) <f0c38945ef01caad6a7c3d4b90a29703264b34a4@microsoft.com>

madhanrm/hcsshim,Microsoft/hcsshim