scripts: twister: add option to force using sysbuild for every testsuite

[nordic-piks]

CLI option which force to use sysbuild.

The usecase:
Enable testing with twister for 'companion' cores, which needs luncher to start.
E.g. Luncher is executed at Application core and FLPR core executes test/sample.
Usage with west:
west build -b nrf54l15pdk/nrf54l15/cpuflpr . --sysbuild -- -DSB_CONFIG_VPR_LAUNCHER=y

Usage with twister:
python ./zephyr/scripts/twister --ninja --jobs 1 -T zephyr/samples/basic --platform nrf54l15pdk/nrf54l15/cpuflpr --device-testing --device-serial /dev/ttyACM0 --extra-args SB_CONFIG_VPR_LAUNCHER=y --west-flash --force-sysbuild

[nordic-piks]

FYI @masz-nordic

[nordic-piks]

This is supplement for #71348

[PerMac]

@nashif @golowanow @hakehuang this is a rather trivial extension, similar to other we already use (e.g. --fixture, --extra-args, etc.) to pass an argument from the top twister call (CLI level) down to all builds

[nashif]

@nashif @golowanow @hakehuang this is a rather trivial extension, similar to other we already use (e.g. --fixture, --extra-args, etc.) to pass an argument from the top twister call (CLI level) down to all builds

I am not convinced this is trivial, maybe in the way it is implemented, however, it is very specific to a single usecase and needs additional command line options which makes it more custom and not generic, something like this need to be implemented at the test level and not be done using twister command line. Did you consider other options?

[PerMac]

@nashif I get your point. I also prefer that if this is a platform config level info, it is added there, and not through twister call. This is an alternative solution #73790
Although I think this PR in general is ok. It's just like with --extra-args, if developer want to check some extra config (in this case using sysbuild) without reworking dozens of yamls, they can pass it through twister's cli