Use kairos-tx for L1 deposit transactions

[koxu1996]

This PR proposes changes to the smart contract to incorporate a full transaction format for L1 deposit events, aiming to standardize them with L2 transactions.

Rationale

• Standardize the transaction structure across Kairos, ensuring consistency and ease of processing.
• Facilitate the generation of a transaction hash for L1 deposits, akin to those for L2 transactions, thereby improving traceability and verification capabilities.

Proposed Changes

Modify the smart contract so that users making L1 deposits will be required to provide "deposit transaction" data matching the L2 format through a smart contract entry point. This data must align with the amount of tokens transferred and the identity of the transaction caller, ensuring consistency and integrity between L1 deposits and the L2 transaction format.

NOTE: Build is currently failing because of kairos-l1-utils introduced in feature/deposit-contract.

Discussion Points

1. Security: Does requiring signatures for all transactions, including those from L1, potentially increase security?
2. Consistency and Integrity: By generating a transaction hash for deposits, we enhance the integrity and auditability of our records. How significant is this advantage?
3. Comparison with Other L2s

Feedback and Future Discussion

This PR is tagged with "needs-discussion" to engage the team in evaluating the benefits and implications of integrating a unified transaction format. Feedback and discussions on this proposal are expected to occur after the MVP phase, as it is not an immediate requirement for the initial launch.

---

Future work

1. Rebase PR after smart contract is merged (Improved version of Deposit contract #51).
2. Fix kairos_crypto compatibility with no_std - kairos-crypto - split trait and introduce no_std support #123.
3. Fix kairos_tx compatibility with no_std - Use rasn fork that is fully compatible with no-std #126.
4. Update tests.
5. Mark PR as ready.