fixing issue where SMB share paths cannot resolve with CRI-containerD on Windows

[marosset]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR fixes:

Partially Fixes #94213

Special notes for your reviewer:

Here is the equivalent PR that went into csi-proxy: kubernetes-csi/csi-proxy#98

As mentioned in the comments the underlying issue here is the behavior of the EvalSymlinks call in golang on Windows.
This change is intended as a work-around until a version of containerD for Windows is built with a versin of golang containing the fix (golang/go#42096)

Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[marosset]

/sig windows
/sig storage
/milestone v1.20
/cc @andyzhangx @jingxu97

[marosset]

/test pull-kubernetes-e2e-aks-engine-azure-windows

[jingxu97]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jingxu97, marosset

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• staging/src/k8s.io/mount-utils/OWNERS [jingxu97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[marosset]

/hold
I want to do a little bit more validation before this merges.

[andyzhangx]

/priority important-soon
/triage accepted

[marosset]

/hold cancel

I tested these changes with a private kubelet running on nodes configured with both docker and containerd.
In both cases I was able to create PVCs using the kubernetes.io/azure-file storage class and successfully schedule containers that used those PVCs.

[andyzhangx]

@marosset should we cherry-pick this PR to old releases? what's the minimum supported k8s version for containerd on Windows?

[marosset]

@andyzhangx I was planning on backporting this to v1.19 this week.