[fix][broker] Fix the applying of namespace policies

[nodece]

Motivation

I'm using the rate limiter on the replicator, when an existing topic is initializing, and the replicator's cursor exists, the topic will create the replicator, and then load and apply the namespace and topic policies to the topic(which includes the replicator), but I found the rate limiter doesn't work.

The namespace policies will not be applied to the replicator after the broker restart.

When will this happen:

• The topic policies are disabled.
• The topic policies are enabled, and there are no policies.

Modifications

• Loading the compaction service and replicator after the namespace and topic policies are loaded
• When there are no topic policies, apply the namespace policies to the topic
• Add resourceGroup, encryptionRequired, and allowAutoUpdateSchema to the HierarchyTopicPolicies to unify the policies

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

[nodece]

This call thread is getOrderedExecutor().

[liudezhi2098]

Check CI errors first

[nodece]

/pulsarbot rerun-failure-checks

[nodece]

cursor.config equals getManagedLedger().getConfig().

When the topic is loaded, org.apache.pulsar.broker.service.persistent.PersistentTopic#checkPersistencePolicies will be called, which changes the ledger config, but the cursor.config will not be changed, so we need to fix that to get the latest config.

BTW, the cursor.conf should be deleted, and we should always call the getManagedLedger().getConfig().

[nodece]

@liudezhi2098 The CI has been passed.

[nodece]

Closed by #22890