Clock tree: hardware alignment and usability improvements

[RecursiveError]

Now that the clock tree–generated information appears to be consistent with the data produced in the .ioc file generated by CubeMX, it’s time to move on to the second stage.

At the moment, the generated information is not very useful if it cannot be applied directly to hardware configuration. For this reason, the current focus is on testing usability and, ultimately, aligning the clock tree model with real hardware configuration requirements.

Goals

• Improve usability of clock tree outputs
• Make generated data directly applicable to hardware configuration
• Align the clock tree model with real hardware constraints

Ideas already under consideration

• Mandatory hardware configurations should not be optional (nullable)
• Convert clock output values from f32 to u32
• Generate each clock tree dynamically

issue tracking:

• add missing flags #9
• format enums to be compatible with the hardware. #10
• create a patch system #11
• improve usability on MicroZig #12