fix(ICofhe): add securityZone parameter to Utils.inputFromHashAndProof

[amathxbt]

Summary

Utils.inputFromHashAndProof in contracts/ICofhe.sol always constructs an EncryptedInput with securityZone: 0, regardless of the actual security zone the ciphertext was created for. This silently breaks any caller that uses a non-zero security zone.

Bug

// Before
function inputFromHashAndProof(bytes32 hash, bytes memory signature, uint8 utype)
    internal pure returns (EncryptedInput memory)
{
    return EncryptedInput({
        ctHash: uint256(hash),
        securityZone: 0,    // ← always 0, ignores multi-zone configurations
        utype: utype,
        signature: signature
    });
}

Impact: When a ciphertext is created on security zone 1 (or any zone ≠ 0) and the caller builds its EncryptedInput via inputFromHashAndProof, the resulting struct has securityZone: 0. The CoFHE task manager then validates the input against zone 0's public key rather than zone 1's, causing verifyInput to fail with a cryptographic verification error that is difficult to diagnose.

All other inputFrom* helpers (inputFromEuint8, inputFromEuint64, etc.) correctly propagate securityZone from the input struct. inputFromHashAndProof is the only outlier.

Fix

Add a four-argument overload that accepts an explicit securityZone parameter. The original three-argument signature is kept as a backward-compatible convenience wrapper defaulting to zone 0.