Scan all top level modules

[henriquevcosta]

I've been trying to roll out the use of this action across a large organisation and it's undesirable for us to have to configure all modules in a multi-module project.
Would it be possible to enable in this action the alternative module semantics described in https://docs.veracode.com/r/r_beginscan#parameters, namely for the scan_all_top_level_modules parameter?

We tried running this action with include: '*' and got the error

[2024.03.26 15:14:06.698] * Action "BeginScan" returned the following message:
[2024.03.26 15:14:06.698] * Module list must contain only top level module ids for the scan.

I assume that it is because there are inter-module dependencies so some aren't top-level.