apollo_l1_provider: create l1 message provider config struct

[ArniStarkware]

In this PR, we create the struct L1MessageProviderConfig.

[reviewable-StarkWare]

This change is 

[ArniStarkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• apollo_node: refactor create_l1_scraper #8159
• apollo_l1_provider: add validation to the l1 provider cooldown #8077
• apollo_node: use l1 message provider config in node config #8076
• apollo_l1_provider: create l1 message provider config struct #8075 👈 (View in Graphite)
• apollo_l1_provider: move l1 scraper config to dedicated config file #8074
• apollo_l1_provider: move l1 provider config to dedicated config file #8073
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[guy-starkware]

Reviewed all commit messages.
Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @giladchase)

---

crates/apollo_l1_provider/src/config.rs line 33 at r1 (raw file):

        ];

        sub_configs.into_iter().flatten().collect()

I'm not sure what the final structure would be in this case. Would it just have two fields: l1_provider_config and l1_scraper_config? I think maybe there's a way to do this without vec! and the flatten that would make that more obvious.

Also, you probably want to run the binary that produces the config json files.

[ArniStarkware]

crates/apollo_l1_provider/src/config.rs line 33 at r1 (raw file):

Previously, guy-starkware wrote…

I'm not sure what the final structure would be in this case. Would it just have two fields: l1_provider_config and l1_scraper_config? I think maybe there's a way to do this without vec! and the flatten that would make that more obvious.

Also, you probably want to run the binary that produces the config json files.

Regarding how unreadable this flatten is - fixed. Thanks - I hate it.

This struct is not used anywhere in this PR. It is first used in the next PR: #8076.
You can see the result of the run of the binary in the next PR.

[guy-starkware]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @giladchase)

[ArniStarkware]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @giladchase)

---

crates/apollo_l1_provider/src/config.rs line 24 at r2 (raw file):

    pub l1_provider_config: L1ProviderConfig,
    pub l1_scraper_config: L1ScraperConfig,
}

As discussed with @guy-starkware .
We should consider making this a flat configuration, which will replace both L1ProviderConfig and L1ScraperConfig.

Code quote:

#[derive(Clone, Debug, Default, Serialize, Deserialize, Validate, PartialEq)]
pub struct L1MessageProviderConfig {
    pub l1_provider_config: L1ProviderConfig,
    pub l1_scraper_config: L1ScraperConfig,
}