Avoid nil pointer for authorizationPolicy

[labuladong]

broker:
  replicaCount: 1
  component: broker
  authorizationPolicy: null  # Explicitly set to null

Explicitly set to null will cause NPE.

[Copilot]

Pull Request Overview

This PR adds nil pointer safety checks to authorization policy templates across multiple Helm charts by verifying that the parent authorizationPolicy object exists before accessing its child properties (from and to).

Key Changes:

• Added parent object existence checks using and operator in conditional statements
• Applied consistently across zookeeper, broker, bookkeeper, and autorecovery authorization policy templates
• Prevents template rendering errors when authorizationPolicy is nil/undefined

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
charts/sn-platform/templates/zookeeper/zookeeper-authorizationpolicy.yaml	Added nil checks for zookeeper.authorizationPolicy before accessing .from and .to
charts/sn-platform/templates/broker/broker-authorizationpolicy.yaml	Added nil checks for broker.authorizationPolicy before accessing .from and .to
charts/sn-platform/templates/bookkeeper/bookkeeper-authorizationpolicy.yaml	Added nil checks for bookkeeper.authorizationPolicy and autorecovery.authorizationPolicy before accessing .from and .to
charts/sn-platform-slim/templates/zookeeper/zookeeper-authorizationpolicy.yaml	Added nil checks for zookeeper.authorizationPolicy before accessing .from and .to
charts/sn-platform-slim/templates/broker/broker-authorizationpolicy.yaml	Added nil checks for broker.authorizationPolicy before accessing .from and .to
charts/sn-platform-slim/templates/bookkeeper/bookkeeper-authorizationpolicy.yaml	Added nil checks for bookkeeper.authorizationPolicy and autorecovery.authorizationPolicy before accessing .from and .to

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

@labuladong:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)