Support configuring DeleteInactiveTopic setting in namespace policy

[315157973]

Fixes #7485

Motivation

Support configuring DeleteInactiveTopic setting in namespace policy

Modifications

Only the two parameters brokerDeleteInactiveTopicsMode and brokerDeleteInactiveTopicsMaxInactiveDurationSeconds support namespace policy. The parameters are changed to Map structure, the key is the namespace, and the value is the parameter value.
Such as: namespace1=delete_when_no_subscriptions, namespace2=delete_when_no_subscriptions.

In addition, there is a key name called default. If it is set, other namespaces that do not specify parameters will use this parameter.
Such as: default=delete_when_no_subscriptions

Verifying this change

InactiveTopicDeleteTest.java

(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

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API: (yes / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

[codelipenghui]

@315157973 We should support settings in pulsar-admin namespaces not in the broker.conf. If the policy is set at the namespace level, we should apply the namespace level settings. Otherwise, use the broker level settings.

[codelipenghui]

The changes look good and I think there are some situation needs to be clarified:

1. If users do not specify the namespace level policy, use broker level config as default.
2. Users can clear the namespace level policy, after that, we should use broker level configurations, So recommend adding clear-inactive-topic-policy here.
3. If the namespace level policy specified, after the broker restart, we should apply the namespace level policy.

[codelipenghui]

/pulsarbot run-failure-checks

[merlimat]

I think this should be part of the same structure that is already used for topic auto-creation, since auto-creation and auto-deletion are tightly related

[codelipenghui]

@merlimat Do you mean we should change InactiveTopicPolicy to TopicAutoDeletionPolicy? And change the command in the namespaces to set-topic-auto-creation, get-topic-auto-creation?

[wolfstudy]

I think this should be part of the same structure that is already used for topic auto-creation, since auto-creation and auto-deletion are tightly related

Sorry @merlimat I merged into this pull request by mistake. If necessary, can we revert this change or open a new issue to fix the corresponding problem?