fix: detect duplicate page tokens in REST catalog listing methods

[waterWang]

Detect duplicate page tokens in RESTSessionCatalog pagination to prevent infinite loops when a REST catalog server returns a repeated next-page-token.

Problem

RESTSessionCatalog.listTables(), listNamespaces(), and listViews() all use a do-while loop that continues as long as nextPageToken != null. If a REST catalog server returns a token that the client has already seen, the loop never terminates — each repeated response is also added to the result builder, so memory use and request volume grow unbounded.

Fix

Track every page token used by each listing call with a HashSet<String>. If the set already contains the token, throw IllegalStateException with a clear error message before the next request.

Changes

• RESTSessionCatalog.java: Added seenPageTokens set and duplicate detection guard to listTables(), listNamespaces(), and listViews()
• TestDuplicatePageToken.java: New test class verifying all three methods throw on a repeated page token

[uros-b]

Suggested change

	}
	}

[uros-b]

Also, one note below regarding testing coverage

[uros-b]

Coverage gap on the new guard code path. All three tests assert only the throw, driven by an always-"stuck" server that repeats one token immediately. There is no positive test proving the guard leaves a valid multi-page listing intact (distinct tokens across N pages, null terminator, all results returned), and none covering the alternating-token loop (A to B to A to B) that the full-HashSet design specifically exists to catch. A no-throw happy-path test plus an alternating-token test should be added so a future regression in the guard (for example a stray double-add of the "" sentinel) that silently truncates real listings would be caught. Live regression risk is bounded because the existing CatalogTests/RESTCatalog pagination suites exercise normal multi-page listing, which is why this is minor rather than blocking, but the strengthening belongs in this PR since it introduces the new code path.