apollo_consensus_orchestrator: remove some panics from context

[matan-starkware]

eth to fri rate: discussed solution on slack, needed due to historic blocks.
client errors: if a remote component disconnects this shouldn't cause us to panic

[reviewable-StarkWare]

This change is 

[matan-starkware]

• apollo_consensus_orchestrator: remove some panics from the validate proposal flow #8048
• apollo_consensus_orchestrator: remove some panics from context #8047 👈 (View in Graphite)
• main-v0.14.0

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

[AlonLStarkWare]

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

---

crates/apollo_consensus_orchestrator/src/sequencer_consensus_context.rs line 753 at r1 (raw file):

                Ok(response) => break response,
                Err(BatcherClientError::BatcherError(e)) => {
                    panic!("Failed to add decision due to batcher error: {e:?}");

Beyond the scope of this PR but should this cause a panic? maybe add a TODO if it shouldn't
(same for the other methods that wrap client calls)

[AlonLStarkWare]

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

[ShahakShama]

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

---

crates/apollo_consensus_orchestrator/src/sequencer_consensus_context.rs line 753 at r1 (raw file):

Previously, AlonLStarkWare (Alon-Lukatch-Starkware) wrote…

Beyond the scope of this PR but should this cause a panic? maybe add a TODO if it shouldn't
(same for the other methods that wrap client calls)

For now yes

[ShahakShama]

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