Incorrect memory sizes tracking issue

[Dirbaio]

If you've got a chip where the stm32-metapac/memory.x feature generates a wrong memory.x please post here.

Identified cases:

• STM32G030K8 flash generates 32kb but has 64kb
• STM32WL55JC ram generates 12kb but has 64kb

[TaylorCarpenter]

STM32WB55VG ram generates 128kb but has 192kb.

[phycrax]

STM32G030C8 flash generates 32kb but has 64kb

[trepidacious]

stm32g491re memory.x shows 32kb RAM, chip should have 112kb (3 blocks of 80, 16, 16)

[Dirbaio]

STM32F303ZE says it has 64k but only has 48kb https://github.com/embassy-rs/stm32-data-generated/issues/1 nope, it's indeed 64k?
stm32u5a5zj says it has 32k but it has 2.5mb or something

[eZioPan]

Chip	Type	memory.x	DS Tab.2	Note
STM32F411RE	RAM	64K	128 KB

markdown if need

|     Chip    |  Type  | memory.x | DS Tab.2  |        Note        |
| :---------: | :----: | :------: | :-------: | :----------------: |
| STM32XDDDXX |  RAM   |  ddd K   |  ddd KB   |                    |
|             | FLASH  |  ddd K   |  ddd KB   |                    |

[eZioPan]

Chip	Type	memory.x	DS Tab.2	Note
STM32H5[67]xx[IG]	RAM	256 K	640 (256+64+320) KB

[Dirbaio]

Chip	Type	memory.x	actual	Note
STM32F051R8T6	RAM	7 K	8 KB	#437

[LorenzoCucchi]

Chip	Type	memory.x	actual	Note
STM32F756ZG	RAM	320K	256K

64 K less since DTCM starting at 0x20000000 is not used, and RAM starts at 0x20010000.

[adri326]

Chip	Type	memory.x	DS Tab.2	Note
STM32L4A6ZG	RAM	320K	256K

Opposite issue to the one above: SRAM correctly starts at 0x2000_0000 up through 0x2004_0000, but the last 64K aren't available. According to the doc, there's a second SRAM2 memory device with 64K size, mapped both to 0x1000_0000 (which is present in the generated STM32L4A6ZG.json, although it has size 0), and to 0x2004_0000

[spcan]

STM32F746ZG variant presents the same issue as the STM32F756 variant described before in this thread.

Chip	Type	memory.x	Actual	Note
STM32F746ZG	RAM	320K	256K

64K less because DTCM should not be counted. RAM starts at 0x20010000 not at 0x20000000.

Consider separating SRAM1 (240K) and SRAM2 (16K).