Access ECS OpenAPI using the VPC endpoint on ECS

[huww98]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

#449 seems to want to enable VPC endpoint for the listed 19 regions, but ended up using public endpoint for them and use VPC endpoint for other regions. Now we are sure the listed 19 (actually 18) regions support VPC endpoint, and we have been using VPC endpoint for other regions for years without problem. So this change should be safe.

For the listed regions:

• ap-south-1: already closed
• cn-north-2-gov-1: manually checked ecs-vpc.cn-north-2-gov-1.aliyuncs.com is accessable
• All other regions are listed in the official doc: https://help.aliyun.com/zh/ecs/developer-reference/call-api-operations-over-the-internal-network?spm=a2c4g.11186623.0.0.10ce48d1z8j7YM

Now VPC endpoint is available for all regions, we should use them by default so that we don't rely on Internet access.

We enable VPC endpoint with a new envvar ALIBABA_CLOUD_NETWORK_TYPE, to try to not breaking the users who deploy CSI on non-ECS env.

If ALIBABA_CLOUD_NETWORK_TYPE is set to:

• vpc: always use ecs-vpc.<region-id>.aliyuncs.com
• public: always use ecs.<region-id>.aliyuncs.com
• unset: use SDK built-in logic: basically, looking up a hard-coded map and fallback to ecs.<region-id>.aliyuncs.com

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

For internal mode, we always use localAPI endpoint, like ecs-openapi-share.cn-beijing.aliyuncs.com, queried from location-readonly.aliyuncs.com

Some regions also can resolve public endpoint to VPC VIP. But this is not documented, not supported in all regions, and can be affected by the custom DNS config. So we should not rely on this.

Does this PR introduce a user-facing change?

We now access ECS OpenAPI using the VPC endpoint on ECS. Please ensure any custom network policy allows such access.

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

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: huww98
Once this PR has been reviewed and has the lgtm label, please assign mowangdk for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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