[improve][pip] PIP-368: Support lookup based on the lookup properties

[RobertIndie]

Motivation

Currently, the lookup process uses only the topic name as its parameter. However, to enhance this process, it's
beneficial for clients to provide additional information. This could be done by introducing the lookupProperties field
in the client configuration. Clients can then share these properties with the broker during lookup.

On the broker side, the broker could also contain some properties that are used for the lookup. We can also support the
lookupProperties for the broker. The broker can use these properties to make a better decision on which broker to
return.

Here is the rack-aware lookup scenario for using the client properties for the lookup:
Assuming there are two brokers that broker-0 configures the lookup property "rack" with "A" and broker-1 configures the
lookup property "rack" with "B". By using the lookup properties, clients can supply rack information during the lookup,
enabling the broker to identify and connect them to the nearest broker within the same rack. If a client that configures
the "rack" property with "A" connects to a lookup broker, the customized load manager can determine broker-0 as the
owner broker since the broker and the client have the same rack property.

Modifications

Add new configuration lookupProperties to the client. While looking up the broker, the client will send the properties
to the broker through CommandLookupTopic request.

The lookupProperties will then be added to the LookupOptions. The Load Manager implementation can access
the properties through LookupOptions to make a better decision on which broker to return.

The properties are used only when the protocol is the binary protocol, starting with pulsar:// or pulsar+ssl://, or
if the loadManagerClassName in the broker is a class that implements the ExtensibleLoadManager interface.

To support configuring the lookupProperties on the broker side, introduce a new broker
configuration lookupPropertyPrefix. Any broker configuration properties that start with the lookupPropertyPrefix
will be included into the BrokerLookupData and be persisted in the metadata store. The broker can use these properties
during the lookup.

In this way, to support the rack-aware lookup scenario mentioned in the "Motivation" part, the client can set the rack
information in the client lookupProperties. Similarly, the broker can also set the rack information in the broker
configuration like lookup.rack. The lookup.rack will be stored in the BrokerLookupData. A customized load manager
can then be implemented. For each lookup request, it will go through the BrokerLookupData for all brokers and select
the broker in the same rack to return.

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

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

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

Matching PR in forked repository

PR in forked repository:

[github-actions]

@RobertIndie Please add the following content to your PR description and select a checkbox:

- [ ] `doc` <!-- Your PR contains doc changes -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update later -->
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->

[RobertIndie]

The vote has passed with 3 binding +1s. https://lists.apache.org/thread/z0t3dyqj27ldm8rs6nl5jon152ohghvw