improve the existing solution with multiple HashMap structs

[etolbakov]

It feels that these number of structs is excessive:

excalidocker-rs/src/main.rs

Lines 143 to 147 in 99459d0

	let mut components = Vec::new();
	let mut container_name_rectangle_structs = HashMap::new();
	let mut container_name_to_point = HashMap::new();
	let mut container_name_to_parents: HashMap<&str, DependencyComponent> = HashMap::new();
	let mut container_name_to_container_struct = HashMap::new();

During the development I came up with the most straightforward solution and didn't have much time to reflect on the optimal one, but maybe we can reduce the number of HashMap structs.

[etolbakov]

As per suggestion I received

To address this issue, I suggest refactoring the code to use a single HashMap with a custom struct to store the different types of data associated with container names. This approach would help simplify the codebase and reduce redundancy.