Revisit TableView/Builder Listener Interface

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Motivation

Currently, the table view handler registration interface, `foreachListen and listen` needs to be called after the tableView.start(). However, some messages could be missed(not handled) if the handlers are registered too late.

The current handlers cannot differentiate existing and tailing messages. Some business logic might need to handle them differently.

### Solution

We probably need to revisit TableView/Builder interface to resolve the above issues correctly.

### Alternatives

Unknown

### Anything else?

N/A

### Are you willing to submit a PR?

- [x] I'm willing to submit a PR!

Start by reading the TableView/Builder interface and the current tableView.start(), foreachListen, and listen registration flow. Clarify an interface design that prevents messages from being missed and lets handlers distinguish existing messages from tailing messages; done when both behaviors are specified and covered by appropriate tests.

Written by the indexing model from the issue text.