Currently, the GatewayZEVM contract's ZETA deposit functions (deposit(), depositAndCall(), depositAndRevert()) expect WZETA tokens from the protocol. This creates an inefficient flow:

Current flow:

1. Protocol mints native ZETA
2. Protocol wraps ZETA → WZETA
3. Protocol calls deposit() on GatewayZEVM with WZETA
4. GatewayZEVM unwraps WZETA → native ZETA
5. GatewayZEVM transfers native ZETA to target

Desired flow:

1. Protocol mints native ZETA
2. Protocol calls deposit() on GatewayZEVM with native ZETA
3. GatewayZEVM transfers native ZETA to target