Update default l1 gas price value, add CLI arg

[AntonD3]

What 💻

• The default l1 gas price value was changed from 50 gwei to 1 gwei
• CLI argument to set the l1 gas price was added

Why ✋

With the l1 gas price of 50 gwei, the gas price per pubdata is 17 * 5010^9 / 250000000 = 3400. It means that we can publish only 8010^6 / 3400 ~ 23529 bytes of the pubdata in one tx(with 80*10^6 gas limit). That's definitely not enough for the tests, usually, contracts are bigger. Also, the possible solution was to increase the gas limit instead, as I know, that's allowed to have a bigger gas limit when the gas is spent on the pubdata, but it can cause issues when the transaction wants to spend more on computation. I think it makes sense to think about it when the gas limit estimation will be implemented.

[MexicanAce]

Can we avoid having another CLI argument in favor of a new RPC endpoint in the CONFIG namespace? e.g. config_setL1GasPrice(gasPrice: u64)

The idea would be to have the test node configuration editable without restarting the node.

Example (Would go in https://github.com/matter-labs/era-test-node/blob/main/src/configuration_api.rs):

#[rpc(name = "config_setL1GasPrice", returns = "u64")]
fn config_set_l1_gas_price(&self, gas_price: u64) -> Result<u64>;

// ...

fn config_set_l1_gas_price(&self, gas_price: u64) -> Result<u64> {
    let mut inner = self.node.write().unwrap(); // We're cleaning up `.unwrap()` use, just leaving here for simplicity
    inner.l1_gas_price = gas_price;
    Ok(inner.l1_gas_price)
}

[AntonD3]

Have not seen it, but sounds good. Will take a look, thanks

[MexicanAce]

Closing stale PR