fix(dotNS): support paginated pending claims with legacy fallback

[pgherveou]

Summary

• read DotnsPopController.pendingClaims(address,uint256,uint256) in bounded pages
• fall back to pendingClaims(address) for older controller deployments
• treat a revert after pagination starts as a read error instead of silently dropping claims
• add calldata, pagination, expiry, fallback, in-core transport, and live Asset Hub coverage

Why

The freshly wiped Paseo Asset Hub controller removed the one-argument pendingClaims view. The old selector reverted with empty data, and the host interpreted that as no pending claims, so an attested username never appeared during polling.

This overlaps #574, which contains the minimal selector/paging change. This version additionally preserves compatibility with older deployments and adds end-to-end live regression probes.

Verification

• cargo test -p truapi-server --lib: 762 passed before the final rebase
• cargo test -p truapi-host-cli: 221 passed, with network tests ignored by default
• focused pending-claim tests: 3 passed after rebasing onto current main
• in-core identity transport regression: passed after rebase
• server and live-test clippy with -D warnings: passed
• live paginated-ABI probe: passed
• live resolution of a real pending username: passed

Related: #573.

[pgherveou]

Closing in favor of #574.