feat(l1): parse l2 to l1 message (#352)

# What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `cargo fmt`.

---------

Signed-off-by: Danil <deniallugo@gmail.com>

chain-events/src/block_events.rs

@@ -12,7 +12,7 @@ use futures::{Sink, SinkExt, StreamExt};
 use client::{
     zksync_contract::{
         codegen::{
-            BlockCommitFilter, BlockExecutionFilter, BlocksVerificationFilter, CommitBlocksCall,
+            BlockCommitFilter, BlockExecutionFilter, BlocksVerificationFilter, CommitBatchesCall,
         },
         parse_withdrawal_events_l1,
     },
@@ -282,7 +282,7 @@ where
 
             let mut events = vec![];
 
-            if let Ok(commit_blocks) = CommitBlocksCall::decode(&tx.input) {
+            if let Ok(commit_blocks) = CommitBatchesCall::decode(&tx.input) {
                 let mut res = parse_withdrawal_events_l1(
                     &commit_blocks,
                     tx.block_number