feat: kafka support custom sasl

[caiq1nyu]

there are some differences in the use of SASL across different versions and architectures of Kafka. this pull request provides an authentication solution that is compatible with all existing versions.

# SASL settings
sasl:
  enable: false
  # if true, the built-in SASL server callback handler in the knowledge base is used, and users are managed by modifying the key.
  # if false, use kafka native SASL callback handler
  # server.properties: 
  #   useKBBuildInSasl=true -> sasl.server.callback.handler.class=${KBClassName}
  #   useKBBuildInSasl=false -> sasl.server.callback.handler.class=''
  useKBBuildInSasl: true
  # [PLAIN,SCRAM-SHA-256,SCRAM-SHA-512]
  # when useKBBuildInSasl=true, only supported [PLAIN] yet. SCRAM-SHA-256, SCRAM-SHA-512 will be comming soon
  mechanisms:
    - PLAIN
  # should be one of sasl.mechanisms setting  
  interBrokerProtocol: PLAIN

this PR includes built-in SASL (useKBBuildInSasl=true) which only supports mechanisms=plain, future versions will support SCRAM.

users can dynamically maintain their accounts by directly editing the account-secret:

stringData:
  # accounts: |
  # [mechanism=PLAIN] format:
  #   {accountName}:{md5Password}
  accounts: ""

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (24c03b8) to head (5b9334b).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #2259   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files         72      72           
  Lines       9500    9482   -18     
=====================================
+ Misses      9500    9482   -18     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[shanshanying]

would it be better to set accounts through helm values

[caiq1nyu]

custom accounts are generally not created during cluster first create; addon users need to add or modify this secret during use.

[apecloud-bot]

/cherry-pick release-1.0

[apecloud-bot]

🤖 says: cherry pick action finished successfully 🎉!
See: https://github.com/apecloud/kubeblocks-addons/actions/runs/19694610860