Fix Paginator dropping results on empty token pages

The Paginator stopped iterating at the first empty page even when the
response carried a non-empty next_page_token, silently dropping results
on later pages. Token-paginated list methods (e.g. tables().list()) can
return empty intermediate pages with a valid token, so results could be
under-returned.

Replace the public Paginator constructor with two explicit factories:
  - Paginator.newTokenPagination: iterate until nextPageFn returns null;
    empty pages are skipped, not treated as the end of results.
  - Paginator.newOffsetPagination: stop on the first empty page (offset,
    SCIM and legacy SQL APIs have no token and rely on this).
The constructor is now private, so every call site states its strategy.

Regenerate all *API.java list methods to the appropriate factory. Update
hand-written APIs: SharesExtAPI -> newTokenPagination; SCIM
Users/Groups/ServicePrincipals (and Account* variants) -> newOffsetPagination.

Signed-off-by: Hector Castejon Diaz <hector.castejon@databricks.com>

Author: hectorcast-db

NEXT_CHANGELOG.md

@@ -6,8 +6,12 @@
 
 ### Breaking Changes
 
+* The public `Paginator` constructor in `com.databricks.sdk.support` has been replaced by the `Paginator.newTokenPagination(...)` and `Paginator.newOffsetPagination(...)` factory methods, which make the pagination strategy explicit. Code that constructed `Paginator` directly must switch to one of these factories.
+
 ### Bug Fixes
 
+* Fixed `Paginator` silently dropping results when a token-paginated response returned an empty page with a non-empty `next_page_token`. List methods (e.g. `tables().list()`) now keep paging until the page token is absent instead of stopping at the first empty page.
+
 ### Security Vulnerabilities
 
 ### Documentation