Support for loading history events using size of batches rather than count

Is your feature request related to a problem? Please describe.
Temporal writes event to historystore in a batch which can be of variable sizes. When we query
for a page of event we set the page size based on number of batches we read from database.
This could be a problem if user is writing very large payloads and single batch is large in size.
We may end of loading unnecessary events which we have to throw away when returning the
events back to client based on the page size set by the caller.

Describe the solution you'd like
We need to design a solution which allows us to load events based on size rather than count.

Describe alternatives you've considered
Another alternate is to still load on count but have throttling in place using size of payloads
loaded from DB. Issue #675

Start by tracing the history-store query that sets page size from the number of batches read. Compare loading by batch count with the proposed payload-size approach, and review issue #675 for the throttling alternative. Done means the design prevents unnecessarily loading large event batches while preserving the caller's page-size behavior.