Is your feature request related to a problem? Please describe.

Currently, publish time of message is generate at client side, while multiple client send messages to broker, we can't guarantee that the order of the messages is incremented by the publish time of the message.

Since Pulsar SQL can push down the "publish_time" predicate and use binary search to trim data, this may result in inaccurate data being trimmed.

So, if can support the generation of publish time on the broker side will bring benefits in this scene. Although topic owner(broker) can change, ledger id still can help guarantee that the trimmed data no data loss.

Describe the solution you'd like

Add support for generate publish time at broker side and add options to enable or disable this feature.

This issue is relate to #4823