fix(spark): release native read resources deterministically - #103

## Summary

Fix the shared Linux musl builder failure on `develop` and PRs #103,
#105, #106, #107, and #108 after the upstream lazy-constructor update.

## Changes

Normalize lists rebuilt from list views through the same `reset_offsets`
path as ordinary lists before forwarding their children to layout
writers. Rebuilding a sliced list view can now leave a lazy elements
slice; a flat child writer cannot serialize that expression. This
preserves the existing referenced-element bounds and resolves the slice
without forcing unrelated encodings into canonical arrays.

Keep the existing nullable sliced-list-view regression and add the
non-nullable case.

## CI Failure Analysis

### Status

Pre-existing base-branch regression, independent of the individual PR
changes. The same failure appears on [develop run
42649358621](https://github.com/quantcast/vortex/actions/runs/42649358621)
and every completed failing PR builder inspected (#105–#108).

### Failed Jobs

- `Rust tests (linux-musl)`: test failure in
`layouts::list::reader::tests::sliced_list_chunks_round_trip::case_4_list_view_chunks`.

### Relevant Log Output

```text
Error: Array vortex.slice is not registered for serialization
```

### Correlation With PR Changes

The upstream merge makes array slicing lazy. The list-view branch of
`canonicalize_to_list_parts` forwarded a rebuilt list's lazy elements
directly, while the ordinary-list branch already normalized them. The
Spark PRs do not change this writer; #107 changes separate zone-pruning
code.

### Recommended Next Step

Merge this shared fix into `develop`. The same patch is being applied to
the affected open PR branches so their new builders include the fix
immediately.

## Validation

- Reproduced the exact failing test on unmodified current `develop`
(exit 100, same serialization error).
- `cargo nextest run -p vortex-layout -E 'test(layouts::list::)'`: all
161 tests passed after the fix, including the original failing case and
new non-nullable case.
- `cargo clippy -p vortex-layout --all-targets --all-features -- -D
warnings`: passed.
- Pinned nightly Rust formatting and `git diff --check`: passed.

Local validation ran on macOS; the fresh Linux musl builders will verify
the runner-specific job.

Signed-off-by: Christopher Wirt <[email protected]>

## Summary

Fixes #11364.

Closing a Spark reader currently leaves its Java-owned native read
handles and file caches alive until Cleaner processing. Make that
release explicit and idempotent, while preserving the resources still
needed by derived scans, returned partitions and Arrow batches. Ports
the lifecycle fix from [QC
#103](quantcast#103).

## Changes

- Make `DataSource` and `Scan` implement `AutoCloseable`, retaining
Cleaner fallback. Keep native calls synchronized with explicit close;
fence scan options so their expressions remain alive across JNI.
- Release partitions prefetched by `hasNext()` but never returned.
- Let Spark's owning wrappers close at EOF. Reader and footer cleanup
attempts every close in ownership order and preserves the original
failure.
- Release native partition ownership when Arrow stream allocation or
import fails.
- Reject reads on closed handles with `IllegalStateException`. An open,
exhausted scan still returns `false` from `hasNext()` and throws
`NoSuchElementException` from `next()`.

---------

Signed-off-by: Christopher Wirt <[email protected]>