## Summary

`hamming_clustering_for_ivf_partition` and `get_ivf_partition_info`
resolved the target index with `find(name)` — the first physical segment
only. On a logical IVF_FLAT index made of multiple segments (delta
segments from append-mode `optimize_indices`, or distributed builds
committed via `commit_existing_index_segments`), this silently processed
only the oldest segment: appended rows were excluded and cross-segment
duplicate pairs were never compared, with no error raised.

Both functions now cover **all** segments of the logical index. Delta
segments of one IVF index share centroids, so partition `p` denotes the
same centroid region in every segment; the correct clustering unit is
the union of partition `p`'s rows across all segments in a single
pairwise pass (representative = min row id, so results are
order-independent).

## Changes

- **Rust** (`lance-index::vector::hamming`): all-segments behavior for
both functions. Every selected segment is validated to share
byte-identical global IVF centroids; a mismatch (or missing centroids)
raises a descriptive error naming the diverging segment UUIDs and
partition counts, advising a retrain. New
`hamming_clustering_for_ivf_partition_segments` /
`get_ivf_partition_info_segments` accept explicit segment UUIDs,
following the `prewarm_index_segments` precedent (#7677).
- **Python**: keyword-only `index_segments` argument on
`hamming_clustering_for_ivf_partition` and `get_ivf_partition_info`
(`None` = all segments, the default). Segment-id normalization used in
three places (these wrappers, `prewarm_index`,
`ScannerBuilder.with_index_segments`) is consolidated into
`lance.util._normalize_index_segment_ids`.

## Notes

- Fixes a latent bug: `get_ivf_partition_info` returned `size: 0` for
every partition on v3 index files because the loaded IVF model carries
no partition lengths. Sizes now come from partition storage via
`VectorIndex::partition_size`.
- Behavior tightening: `get_ivf_partition_info` now validates the
indexed column is `FixedSizeList<UInt8, 8>`, a check it previously
skipped. This is consistent with the clustering function, which always
required 8-byte hashes.
- An empty explicit segment selection is rejected rather than silently
returning "no duplicates", to avoid a silent data-quality hazard in
dedup pipelines.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **New Features**
* Added support for running IVF_FLAT Hamming clustering and partition
analysis across multiple index segments.
* Added optional segment selection to limit clustering and partition
statistics to specific physical segments.
* Segment identifiers now accept UUID strings or UUID objects with
validation for invalid selections.

* **Bug Fixes**
* Improved handling and validation of index segment identifiers across
dataset and scanner operations.
* Added validation to ensure selected segments are compatible before
processing.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->