feat(aggregator): support two operator addresses in sender and aggreg…

…ator (#1201)

## What ❔

Adds optional ability to send commit transactions from a separate
operator address on L1.

## 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 `zk fmt` and `zk lint`.
- [ ] Spellcheck has been run via `zk spellcheck`.
- [ ] Linkcheck has been run via `zk linkcheck`.

---------

Co-authored-by: koloz <zach.kolodny@gmail.com>

core/lib/config/src/configs/eth_sender.rs

@@ -115,6 +115,13 @@ impl SenderConfig {
             .ok()
             .map(|pk| pk.parse().unwrap())
     }
+
+    // Don't load blobs private key, if it's not required
+    pub fn private_key_blobs(&self) -> Option<H256> {
+        std::env::var("ETH_SENDER_SENDER_OPERATOR_BLOBS_PRIVATE_KEY")
+            .ok()
+            .map(|pk| pk.parse().unwrap())
+    }
 }
 
 #[derive(Debug, Deserialize, Copy, Clone, PartialEq)]

core/lib/dal/migrations/20240221154502_add-from-addr-to-eth-txs.down.sql

@@ -0,0 +1 @@
+ALTER TABLE eth_txs DROP COLUMN from_addr;

core/lib/dal/migrations/20240221154502_add-from-addr-to-eth-txs.up.sql

@@ -0,0 +1 @@
+ALTER TABLE eth_txs ADD COLUMN from_addr BYTEA;