manifest: Update hal_stm32 to add released binaries of stm32wb

[benothmn-st]

Update hal_stm32 to add the history of the released binaries to be flashed in the Cortex-M0 coprocessor.

[zephyrbot]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
hal_stm32	zephyrproject-rtos/hal_stm32@04ccc77	zephyrproject-rtos/hal_stm32@5dcc08c	zephyrproject-rtos/hal_stm32@04ccc779..5dcc08c1

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[fabiobaltieri]

@benothmn-st @erwango does this needs to go for 4.1? https://github.com/zephyrproject-rtos/hal_stm32/compare/55043bcc35fffa3b4a8c75a696d932b5020aad09..5dcc08c119d421fec7d67555fc7b0aa220288e56 shows quite some extra stuff, is the core change to be considered a fix?

[erwango]

@benothmn-st @erwango does this needs to go for 4.1? https://github.com/zephyrproject-rtos/hal_stm32/compare/55043bcc35fffa3b4a8c75a696d932b5020aad09..5dcc08c119d421fec7d67555fc7b0aa220288e56 shows quite some extra stuff, is the core change to be considered a fix?

Yeah, my bad. This was actually merged w/o manifest update before feature freeze and this shows up now.
This being said, the changes are only pure additions of N6 Ethernet pin configuration (Matching N6 Eth PR is not upstream yet), and config update on the pin generation script (which effects are reflected in the new generated pins).
So technically this is purely no risk, but I understand this could bother you.

[fabiobaltieri]

@erwango your comment leaves me as confused as before :-) pick a milestone

[dkalowsk]

Thanks for the clarification on the milestone details. Looks like a bug fix to me

[fabiobaltieri]

Hey, moving it back to 4.2, bit late for this now.