samples: enable build tests for the ch32v006evt

[nzmichaelh]

The ch32v006evt has 8 KiB of RAM which is enough for many of the basic samples but, by default, Twister assumes that a sample needs 16 KiB of RAM.

Mark some of the samples as needing 8 KiB of RAM so the ch32v006evt gets better CI coverage.

[nzmichaelh]

Note that Twister should fail at the moment, but then pass once #90438 is merged and I rebase.

[nzmichaelh]

Hmm, Twister ran: https://github.com/zephyrproject-rtos/zephyr/actions/runs/15291782992/job/43012659289?pr=90690

but the results don't include the ch32v006evt, but do pass for boards like gd32e103v_eval, frdm_k22f. I'll investigate as I suspect there's a default platform list.

[kartben]

Hmm, Twister ran: https://github.com/zephyrproject-rtos/zephyr/actions/runs/15291782992/job/43012659289?pr=90690

but the results don't include the ch32v006evt, but do pass for boards like gd32e103v_eval, frdm_k22f. I'll investigate as I suspect there's a default platform list.

Twister only runs on integration_platforms: on pull requests and when push to main (i.e. merge). It's only in the weekly CI run that the rest of the platforms are included.

[nzmichaelh]

Hmm, Twister ran: https://github.com/zephyrproject-rtos/zephyr/actions/runs/15291782992/job/43012659289?pr=90690
but the results don't include the ch32v006evt, but do pass for boards like gd32e103v_eval, frdm_k22f. I'll investigate as I suspect there's a default platform list.

Twister only runs on integration_platforms: on pull requests and when push to main (i.e. merge). It's only in the weekly CI run that the rest of the platforms are included.

Thanks. Still sounds worthwhile then, and the developer can do a twister --vendor wch manually.

[kartben]

I'm fine with the change but the commit message is off -- it should simply refer to the fact you're lowering the min RAM requirements

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[kartben]

@nzmichaelh can you please fix the commit message / PR description when you have a chance? (see earlier comments)

[github-actions]

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.