CLPR-5: Hiero Verifier Contracts — on-chain proof verification for peer ledger state

## Epic CLPR-5: Hiero Verifier Contracts

**Parent:** hiero-ledger/roadmap#48
**Repo:** hiero-ledger/hiero-consensus-node

### Objective

Implement verifier system contracts on Hiero's EVM or system contract that validate state proofs from peer ledgers. Verifiers implement the `IClprVerifier` interface and are invoked by the CLPR Service during bundle processing, endpoint roster updates, and configuration verification.

### Background

CLPR is proof-system agnostic. The protocol never inspects proof bytes — it delegates verification to verifier contracts specific to each source ledger's proof format. Verifiers are deployed as EVM system contracts with Hiero AccountIDs, immutably bound to Connections at registration time. The verifier's code hash (`keccak256(bytecode)`) is stored as an informational fingerprint.

### Expected Functionality

1. **IClprVerifier interface** — Solidity interface with `verifyConfig`, `verifyBundle`, `verifyEndpoints`, `verifyMetadata` (all `view`).
2. **HieroTSS verifier** — Validates TSS signatures + SHA-384 Merkle paths for Hiero-to-Hiero communication.
3. **EthereumBLS verifier** — Validates Ethereum sync committee BLS signatures for Ethereum-to-Hiero communication.
4. **Pass-through verifier** — Reference implementation for testing (no cryptographic verification).

### Stories

- CLPR-5.1: IClprVerifier interface, system contract framework, and pass-through verifier
- CLPR-5.2: HieroTSS verifier (Hiero-to-Hiero)
- CLPR-5.3: EthereumBLS verifier (Ethereum-to-Hiero)

### Dependencies

- CLPR-1 (Connection registration stores verifier)
- CLPR-2.3 (SubmitBundle calls `verifyBundle`)
- CLPR-1.6 (UpdateEndpointRoster calls `verifyEndpoints`)

### Spec References

- [Cross-Platform Spec §3](clpr-service-spec.md) — IClprVerifier interface
- [Hiero Impl Spec §5](clpr-hiero-impl-spec.md) — Verifier integration, fingerprint, invocation

Start by reading Cross-Platform Spec §3 in clpr-service-spec.md and Hiero Impl Spec §5 in clpr-hiero-impl-spec.md, then trace the CLPR-1 and CLPR-2.3/1.6 dependency entry points. Done means the IClprVerifier interface, system-contract framework, pass-through verifier, HieroTSS verifier, and EthereumBLS verifier are implemented and invoked for their stated operations.

Written by the indexing model from the issue text.