fix namespace and topic docs / CRDs

[freeznet]

(If this PR fixes a github issue, please add Fixes #<xyz>.)

Fixes #

(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)

Master Issue: #

Motivation

Explain here the context, and why you're making that change. What is the problem you're trying to solve.

Modifications

Describe the modifications you've done.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Documentation

Check the box below.

Need to update docs?

• doc-required

  (If you need help on updating docs, create a doc issue)

• no-need-doc

  (Please explain why)

• doc

  (If this PR contains doc changes)

[github-actions]

@freeznet: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)

[Copilot]

Pull Request Overview

This PR updates the Pulsar topic and namespace documentation to align with new schema formats and expands the namespace CRD and API enums to support additional compatibility strategies.

• Clarified the schema field format in pulsar_topic.md
• Expanded and renamed schema compatibility options in pulsar_namespace.md, CRD YAML, and Go types
• Adjusted kubebuilder validation enums in the PulsarNamespaceSpec Go struct

Reviewed Changes

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

File	Description
docs/pulsar_topic.md	Updated schema table entry to specify JSON string usage
docs/pulsar_namespace.md	Replaced strategy names with new uppercase values and updated descriptions and examples
config/crd/bases/resource.streamnative.io_pulsarnamespaces.yaml	Replaced old enum entries with new compatibility strategy values
api/v1alpha1/pulsarnamespace_types.go	Updated kubebuilder:validation:Enum to include new strategy values

Comments suppressed due to low confidence (1)

docs/pulsar_namespace.md:107

• Restore consistent indentation in the YAML code examples (e.g., re-add leading spaces before schemaCompatibilityStrategy) to maintain proper formatting within the code blocks.

schemaCompatibilityStrategy: ALWAYS_COMPATIBLE