chore(consensus): add ContextConfig to SequencerConcensusContext

[guy-starkware]

This adds the ContextConfig struct from the previous PR unto the SequencerConsensusContext struct.

[reviewable-StarkWare]

This change is 

[guy-starkware]

• chore(consensus): reorder config item #3430
• chore(consensus): move some network parameter consts into config #3380
• chore(consensus): remove some fields from ConsensusConfig #3379
• chore(consensus): add PapyrusConsensusConfig struct #3377
• chore(consensus): update ConsensusManagerConfig with new parameters #3340
• chore(consensus): add ContextConfig to SequencerConcensusContext #3338 👈 (View in Graphite)
• feat(consensus): add config to Context #3268
• chore(consensus): remove default value for chain_id config parameter #2898 : 1 other dependent PR (#3130 )
• main

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

[asmaastarkware]

Reviewed 7 of 7 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @guy-starkware)

[matan-starkware]

Reviewed 13 of 13 files at r2, all commit messages.
Reviewable status: all files reviewed, 3 unresolved discussions (waiting on @guy-starkware)

---

a discussion (no related file):
When you move the struct, I'd like it to be in a file config.rs not inside of the sequencer context file.

---

crates/starknet_integration_tests/src/utils.rs line 150 at r2 (raw file):

            context_config: ContextConfig {
                num_validators,
                chain_id: papyrus_storage::test_utils::CHAIN_ID_FOR_TESTS.clone(),

Is this used elsewhere in testing code?

Code quote:

                chain_id: papyrus_storage::test_utils::CHAIN_ID_FOR_TESTS.clone(),

---

crates/starknet_consensus_orchestrator/src/sequencer_consensus_context.rs line 112 at r2 (raw file):

// has a timeout as a defensive measure to make sure the proposal doesn't live forever if the
// Context crashes or has a bug.
const VALIDATE_PROPOSAL_MARGIN: Duration = Duration::from_secs(10);

These should enter the config. Can be a follow up PR.

Code quote:

const BUILD_PROPOSAL_MARGIN: Duration = Duration::from_millis(1000);
// When validating a proposal the Context is responsible for timeout handling. The Batcher though
// has a timeout as a defensive measure to make sure the proposal doesn't live forever if the
// Context crashes or has a bug.
const VALIDATE_PROPOSAL_MARGIN: Duration = Duration::from_secs(10);

[guy-starkware]

Reviewable status: all files reviewed, 3 unresolved discussions (waiting on @matan-starkware)

---

crates/starknet_consensus_orchestrator/src/sequencer_consensus_context.rs line 112 at r2 (raw file):

Previously, matan-starkware wrote…

These should enter the config. Can be a follow up PR.

Added to Monday board.

---

crates/starknet_integration_tests/src/utils.rs line 150 at r2 (raw file):

Previously, matan-starkware wrote…

Is this used elsewhere in testing code?

In papyrus_storage test_utils and in end_to_end_flow_test.

[asmaastarkware]

Reviewed all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @guy-starkware and @matan-starkware)

---

crates/papyrus_node/src/run.rs line 201 at r2 (raw file):

    let consensus_config = consensus_config.clone();
    let context_config = context_config.clone();
    debug!("Consensus configuration: {consensus_config:?}");

add context_config

[guy-starkware]

Reviewable status: 6 of 13 files reviewed, 2 unresolved discussions (waiting on @asmaastarkware and @matan-starkware)

---

crates/papyrus_node/src/run.rs line 201 at r2 (raw file):

Previously, asmaastarkware (asmaa-starkware) wrote…

add context_config

Done.

[asmaastarkware]

Reviewed 7 of 7 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @guy-starkware and @matan-starkware)

[guy-starkware]

Reviewable status: 10 of 13 files reviewed, 1 unresolved discussion (waiting on @matan-starkware)

---

a discussion (no related file):

Previously, matan-starkware wrote…

When you move the struct, I'd like it to be in a file config.rs not inside of the sequencer context file.

Done.

[guy-starkware]

Reviewed 3 of 13 files at r2, 7 of 7 files at r3, 3 of 3 files at r4, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @matan-starkware)

Already got the LGTM