[improve][broker]fix broker irrational behavior when it is closing

[HQebupt]

Motivation

When the leader broker is closing, and it will release the ownership of its bundles first. The client will redo topic lookup , and this broker will handle it, resulting in unexpected results. For instance, some unassigned bundles maybe are taken ownership by itself again, but the broker can not server the bundles due to it is closing . see the screenshot log.
Therefore, it is necessary to check the status of the broker when handling lookup requests.

Modifications

• Check Pulsar Service state when handling lookup request.
• Add 'Init' state as running state in PulsarService since PulsarFunctionWorker have to lookup topic when broker is starting.

pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/PulsarService.java

Lines 855 to 856 in 4a28c08

	// start function worker service if necessary
	this.startWorkerService(brokerService.getAuthenticationService(), brokerService.getAuthorizationService());

pulsar/pulsar-functions/worker/src/main/java/org/apache/pulsar/functions/worker/PulsarWorkerService.java

Lines 445 to 447 in 4a28c08

	tryCreateNonPartitionedTopic(workerConfig.getFunctionAssignmentTopic());
	tryCreateNonPartitionedTopic(workerConfig.getClusterCoordinationTopic());
	tryCreateNonPartitionedTopic(workerConfig.getFunctionMetadataTopic());

Verifying this change

• Make sure that the change passes the CI checks.

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

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): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (no)

Documentation

Check the box below and label this PR (if you have committer privilege).

Need to update docs?

• doc-not-needed

[HQebupt]

/pulsarbot run-failure-checks

[codelipenghui]

@HQebupt Please check the failed test

[HQebupt]

@HQebupt Please check the failed test

Thank you Penghui. I found the key point.

[HQebupt]

/pulsarbot run-failure-checks

[Jason918]

LGTM

[codelipenghui]

The change looks good to me.

Looks like we also need to check other cases (e.g. handleConnect)
If the broker is shutting down, we should also prevent new connections.