fix: revert alpine base image change to fix DNS issue

[andyzhangx]

What type of PR is this?
/kind bug

What this PR does / why we need it:
fix: revert alpine base image change to fix DNS issue

revert of #1175

On some k8s clusters with customer vnet setting, cifs mount cannot resolve DNS while nslookup works well, and switch to debian-base image works.

• Root cause:
  cifs mount is using getaddrinfo invoked by resolve_host which finally depends on glibc implementation on debian based image, while on alpine image, it's using musl, getaddrinfo may not handle DNS well in lots of cases: github.com not reachable from alpine image alpinelinux/docker-alpine#155, so we decided to using debian base image which are using glibc lib.

other reference: nodejs/docker-node#1030 (comment)

btw, though alpine is updating musl lib which could solve dns-over-tcp (on alpine 3.18), while it's still not suggested to use alpine image since we don't know whether there is other potential dns issue: https://news.ycombinator.com/item?id=35056594

E0901 04:03:22.810456       1 utils.go:81] GRPC error: rpc error: code = Internal desc = volume(rg-aue-dev-mex-api-005#xxx#pvc-832fd08c-9c26-445c-89cf-27be3d21f200###aks-aue-dev-mex-02-apigateway-int) mount //xxx.file.core.windows.net/pvc-832fd08c-9c26-445c-89cf-27be3d21f200 on /var/lib/kubelet/plugins/kubernetes.io/csi/file.csi.azure.com/ab9b06cbec2b8378408965f5085bdd6debe6f12289c8f1549fe17bd96d104fe3/globalmount failed with mount failed: exit status 1
Mounting command: mount
Mounting arguments: -t cifs -o mfsymlinks,actimeo=30,nosharesock,gid=1000,file_mode=0777,dir_mode=0777,<masked> //xxx.file.core.windows.net/pvc-832fd08c-9c26-445c-89cf-27be3d21f200 /var/lib/kubelet/plugins/kubernetes.io/csi/file.csi.azure.com/ab9b06cbec2b8378408965f5085bdd6debe6f12289c8f1549fe17bd96d104fe3/globalmount
Output: mount error: could not resolve address for xxx.file.core.windows.net: Unknown error
E0901 04:03:22.811614       1 mount_linux.go:195] Mount failed: exit status 1

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

fix: revert alpine base image change to fix DNS issue

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

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:

• OWNERS [andyzhangx]

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

[andyzhangx]

/retest

[andyzhangx]

/cherrypick release-1.28

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #1420

In response to this:

/cherrypick release-1.28

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[andyzhangx]

/cherrypick release-1.27

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #1421

In response to this:

/cherrypick release-1.27

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[andyzhangx]

/cherrypick release-1.26

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #1422

In response to this:

/cherrypick release-1.26

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[andyzhangx]

/cherrypick release-1.24

[k8s-infra-cherrypick-robot]

@andyzhangx: new pull request created: #1423

In response to this:

/cherrypick release-1.24

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.