encryptInputs with improved API

[architect-dev]

Refactored encrypt function named encryptInput

Breaks apart the encrypt inputs and options to improve the api. Also introduces the ability to override the sender embedded in the encrypted inputs.

New api:

 const encrypted = await cofhejs
   .encryptInputs([Encryptable.uint128(value)])
   .setSender(paymasterData.address) // optional - defaults to cofhejs initialized sender
   .setSecurityZone(0) // optional - defaults to 0
   .setStepCallback((step) => console.log(step)) // optional - used for debugging and UIs
   .encrypt();

[architect-dev]

This class is responsible for the updated functionality. The types of the inputs are inferred from the parameters, and the types of the outputs are inferred from the inputs.
Ex:
call: cofhejs.encryptInputs([Encryptable.bool(true)])
input types: [EncryptableBool]
output types: [CofheInBool]

The other input parameters (sender / chainId / zk) are provided in the body of cofhejs.encryptInputs. The sender / chainId are pulled from the store, and the zk is created in the multiple entrypoints (in node the zk package uses the tfhe-node builder, and in web it uses the tfhe builder)

[architect-dev]

This is the function that gets exposed as cofhejs.encryptInputs. The state variables are injected here, along with a node specific zkPackProveVerify implementation

[architect-dev]

Tested working implementation against arb-sepolia.

[architect-dev]

Remaining:

• Add the new encryptInputs function to the web endpoint
• Mark the existing encrypt implementation as deprecated
• Better comment the functionality
• Integrate with the mocks so that the zk step gets re-routed to the on-chain mock steps
• Create unit tests

[architect-dev]

@tovi-fhe ready for a look.