Add support for STM32WB

[JackyJia73]

Description

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

• Add support for STM32WB

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[tzarc]

At this stage we're not including core-defined support for new MCUs unless there's at least one corresponding keyboard for them. All of these items can be specified in rules.mk directly inside a keyboard definition -- it'll be up to the QMK team to determine if/when we should be breaking it out and making a common definition.

[tzarc]

See #23392 as an example of in-keyboard definition.

[JackyJia73]

@tzarc How about update a working kb the same time? Thanks

[tzarc]

@tzarc How about update a working kb the same time? Thanks

That’s fine, so long as the definitions for the MCU still reside in the keyboard. QMK maintainers will choose when to support it in core definitions.