fix(esp32c6): report linked RAM usage and preserve build metadata

[zackees]

Reproduction from the regular FastLED checkout on fbuild 2.5.14:

1. Run bash compile esp32c6 --examples AutoResearch --no-interactive.
2. fbuild successfully links and emits the image.
3. The result reports RAM 1.88MB / 320KB (602.5%) and then the FastLED wrapper reports Failed to get metadata for build_info.json (exit code 1).

The image cannot actually consume 602% of the declared RAM and the successful fbuild output is therefore misleading. The metadata failure also leaves no example-scoped build_info file for this target. This needs fbuild-level investigation of ESP32-C6 size-section accounting and/or metadata output so CI does not present a successful build with impossible memory usage.

No deploy or direct flash tool was involved.

[zackees]

Fixed by #1297 (squash-merged as 521c6ff).

Switched ESP32 size reporting from Berkeley format to SysV format (size -A). The Berkeley format lumps .flash.rodata (flash-resident) into the data column alongside .dram0.data (RAM-resident), inflating RAM to impossible percentages (602% on ESP32-C6). SysV format lists each section individually with its name, so parse_esp32_size_sysv classifies sections by prefix: .flash.*/ .rodata* → Flash, .dram0.* → RAM.