chore: add get_http_server_config function

[nadin-Starkware]

Stack:

• feat: add test case for remote connection flow #2647
• chore: add mock_system_mode to create config function #2646
• chore: return vector of SequencerNodeConfig in create config function #2638
• chore: add get_http_server_config function #2637 ⬅
• chore: change sequencer_node_handle type #2636
• chore: add serial_test crate #2635
• chore: add mock system mode enum #2632

⚠️ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

[reviewable-StarkWare]

This change is 

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Please upload report for BASE (spr/main/5edf2768@30e4861). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
crates/starknet_integration_tests/src/utils.rs	0.00%	9 Missing ⚠️

Additional details and impacted files

@@                 Coverage Diff                  @@
##             spr/main/5edf2768    #2637   +/-   ##
====================================================
  Coverage                     ?   34.99%           
====================================================
  Files                        ?      277           
  Lines                        ?    32236           
  Branches                     ?    32236           
====================================================
  Hits                         ?    11281           
  Misses                       ?    19948           
  Partials                     ?     1007           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Itay-Tsabary-Starkware]

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @nadin-Starkware)

---

crates/starknet_integration_tests/src/utils.rs line 292 at r1 (raw file):

        })
        .map(|config| &config.http_server_config)
}

I fear this path is not scalable. When handling different configs there must be a better way than to search one that meets a predicate. What will happen when we'd have a 3rd config? Or 10 configs?
Could we prehaps define a mapping instead of a vector? And maybe let the key be the functionality required?

Code quote:

pub fn get_http_server_config(configs: &[SequencerNodeConfig]) -> Option<&HttpServerConfig> {
    configs
        .iter()
        .find(|config| {
            matches!(
                config.components.http_server.execution_mode,
                ActiveComponentExecutionMode::Enabled
            )
        })
        .map(|config| &config.http_server_config)
}