chore(starknet_sequencer_node): create component configs in deployment

[Itay-Tsabary-Starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[Itay-Tsabary-Starkware]

• chore(starknet_sequencer_node): create component configs in deployment #5093 : 2 dependent PRs (#5092 , #5103 ) 👈 (View in Graphite)
• chore(starknet_sequencer_node): add derive annotations #5043
• chore(starknet_integration_tests): delete redundant mempool p2p config gen fn #5091
• main

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

[Itay-Tsabary-Starkware]

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion

---

crates/starknet_sequencer_node/src/deployment.rs line 177 at r1 (raw file):

                        _ => panic!("Unexpected service name"),
                    }
                }

This can be slightly simplified by creating a all_inner_service_names() fn for DistributedNodeServiceName.
Will do so in a different pr.

Code quote:

                for service_name in service_names {
                    match service_name {
                        ServiceName::DistributedNode(inner_service_name) => {
                            component_config_pair_map
                                .insert(inner_service_name, inner_service_name.into());
                        }
                        _ => panic!("Unexpected service name"),
                    }
                }

[nadin-Starkware]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion

[Itay-Tsabary-Starkware]

Reviewed 2 of 2 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @Itay-Tsabary-Starkware)