Cannot associate a bandwidth package with an internal NLB

[poblahblahblah]

What happened:

When creating a private NLB we cannot associate a bandwidth package and EIP using the annotations. We expected the bandwidth package to be associated with the LB that was created. This silently failed and we ended up needing to engage Aliyun support. Support suggested that this needed to be done through the console.

What you expected to happen:

We would be able to associate a bandwidth package and EIP to a private NLB

How to reproduce it (as minimally and precisely as possible):

We created a Service and attach the following Annotations:

Annotations: 
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-address-type: intranet
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-bandwidth-package-id: cbwp-xxxxxxxxxxxxx
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-cert-id: xxxxxxxxxxxxxx
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-health-check-connect-port: 80
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-health-check-flag: on
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-health-check-httpcode: http_2xx,http_3xx
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-health-check-interval: 10
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-health-check-timeout: 5
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-health-check-type: http
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-health-check-uri: /healthz
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-healthy-threshold: 3
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-master-zoneid: cn-shanghai-g
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-protocol-port: https:443,http:80
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-scheduler: wrr
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-slave-zoneid: cn-shanghai-f
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-spec: slb.s3.large
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-unhealthy-threshold: 3
                          service.beta.kubernetes.io/alibaba-cloud-loadbalancer-vswitch-id: vsw-xxxxxxxxxxxxxxx

Anything else we need to know?:

The solution wasn't obvious to us as there was no error logged by CCM. It would be nice if an unsupported configuration could be logged!

Environment:

• Kubernetes version (use kubectl version): v1.28.9-aliyun.1
• Cloud provider or hardware configuration: Alicloud CS Managed Kubernetes
• OS (e.g: cat /etc/os-release): N/A
• Kernel (e.g. uname -a): N/A
• Install tools: N/A
• Network plugin and version (if this is a network-related bug): N/A
• Others: Using CCM v2.9.1