fix evm access control conditions

[glitch003]

Make EVM Access control conditions implementation match the one in the Node. the thing this fixes is that when the client hashed the access control condition, it was done differently vs the lit node code, so decryption actually succeeded on the node, but we couldn't combine the shares client side, because the hashed access control condition goes into the identity param.

[Copilot]

Pull Request Overview

This PR fixes EVM access control conditions implementation to match the behavior in the Lit Node, resolving an issue where client-side share combination failed due to mismatched hashing of access control conditions between client and node implementations.

• Updated access control condition data types from JSON values to strongly typed fields
• Refactored hashing logic to match the Lit Node implementation
• Added comprehensive test coverage for EVM contract conditions with client-side decryption

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
lit-rust-sdk/src/types.rs	Updated EvmContractCondition and ReturnValueTest structures to use string types instead of JSON values
lit-rust-sdk/src/client/decrypt.rs	Refactored access control condition hashing to match Node implementation
lit-rust-sdk/src/utils.rs	Added utility function for converting bytes to hex string
lit-rust-sdk/tests/encrypt_test.rs	Updated test to use string value instead of JSON for return value test
lit-rust-sdk/tests/decrypt_client_side.rs	Added comprehensive test for EVM contract conditions and updated existing test
lit-rust-sdk/src/lib.rs	Added utils module export
lit-rust-sdk/Cargo.toml	Added ethabi dependency and bumped version

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}