#2491 fix(setup): don't require tensor-data alignment for GGUF shards without …

Descripción

## Change

Skip the tensor-payload extent check when a successfully parsed GGUF shard has no tensors. GGUF parsing, the existing checks for tensor-bearing shards, and the separate pinned size/SHA-256 verification remain unchanged.

`check_shards()` and `whole_shard()` calculated the minimum GGUF shard size as `data_start + max(tensor end offsets)`. For a shard containing no tensors, this incorrectly required the file to extend through the aligned tensor-data start, even though no tensor payload exists.

This caused valid metadata-only GGUF shards to be rejected as truncated. For example, `Qwen3.8-Flash-Next-UD-Q5_K_XL-00001-of-00006.gguf` was reported as six bytes short:

- Actual file size: 10,946,618 bytes
- Parsed tensor count: 0
- Aligned data start: 10,946,624 bytes

The downloaded file matched the size and SHA-256 declared in `setup.py`.


## Title
<!-- If Applicable, reference the GitHub issue -->
Issue: Resolves #2470 and #2346  

## Summary
<!-- Quick Summary of changes -->

## What changed
<!-- Specifics on files changed, and what changes were made there -->

## Extra Notes
<!-- Any extra notes, delete if there are none -->