After Zookeeper opens the SASL PLAN authentication protocol,Does pulsar support SASL's PLAN protocol?

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Motivation

The company requires pulsar to be registered with the external zookeeper. The zookeeper is 3.6.3 and the pulsar version is 2.10.2.

When SASL is not used, pulsar can be registered with zookeeper normally. It can also be deployed and run normally. When SASL is added, the following situation occurs, which indicates that it is not registered with zookeeper. I would like to ask, does pulsar need to support the sasl PLAN protocol to register with zookeeper?

zookeeper note:


pulsar install message:

helm install pulsar2 pulsar-2.9.4.tgz \
--timeout 10m \
--set namespace=paas-middleware \
--set initialize=true \
--set clusterName=pulsar-rsj \
--set volumes.persistence=true \
--set volumes.local_storage=false \
--set zookeeper.volumes.data.local_storage=false \
--set components.zookeeper=false \
--set components.pulsar_manager=false \
--set monitoring.prometheus=false \
--set monitoring.grafana=false \
--set monitoring.node_exporter=false \
--set monitoring.alert_manager=false \
--set proxy.service.type=ClusterIP \
--set images.bookie.repository=registry.cn-hangzhou.aliyuncs.com/renshaojin/pulsar-all \
--set images.bookie.tag=2.10.2 \
--set images.autorecovery.repository=registry.cn-hangzhou.aliyuncs.com/renshaojin/pulsar-all \
--set images.autorecovery.tag=2.10.2 \
--set images.broker.repository=registry.cn-hangzhou.aliyuncs.com/renshaojin/pulsar-all \
--set images.broker.tag=2.10.2 \
--set images.proxy.repository=registry.cn-hangzhou.aliyuncs.com/renshaojin/pulsar-all \
--set images.proxy.tag=2.10.2 \
--set images.functions.repository=registry.cn-hangzhou.aliyuncs.com/renshaojin/pulsar-all \
--set images.functions.tag=2.10.2 \
--set pulsar_metadata.image.repository=registry.cn-hangzhou.aliyuncs.com/renshaojin/pulsar-all \
--set pulsar_metadata.image.tag=2.10.2 \
--set pulsar_metadata.userProvidedZookeepers=zk-hs.paas-public.svc.cluster.local:2181/pulsar \
--set proxy.ports.http=8080 \
--set proxy.ports.https=8443 \
--set extraEnvVars[0].name=JVMFLAGS \
--set extraEnvVars[0].value='${JVMFLAGS} -Djava.security.auth.login.config=/pulsar/conf/zookeeper_jaas.conf' \
--set extraVolumes[0].name=zookeeper-jaas-config \
--set extraVolumes[0].configMap.name=pulsar-zookeeper-jaas-config \
--set extraVolumes[0].configMap.items[0].key=zookeeper_jaas.conf \
--set extraVolumes[0].configMap.items[0].path=zookeeper_jaas.conf \
--set extraVolumeMounts[0].name=zookeeper-jaas-config \
--set extraVolumeMounts[0].mountPath=/pulsar/conf/ \
--set extraVolumeMounts[0].subPath=zookeeper_jaas.conf

configmap message:


The resault is:



why? why?

### Solution

_No response_

### Alternatives

_No response_

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Start by reproducing the external ZooKeeper setup with Pulsar 2.10.2, ZooKeeper 3.6.3, the supplied Helm command, and the mounted JAAS configuration. Inspect the resulting startup and ZooKeeper authentication logs to determine whether SASL PLAN is supported or why registration fails. Done requires a confirmed support status and a clearly scoped change or documentation update.

Written by the indexing model from the issue text.