Create a different verification file if dry run is on This commit is another usability issue: this allows simulating the write of a verification file by resolving all configurations, but instead of modifying the file it actually generates a different one which can then be used for diff'ing.
This can be useful whenever the user wants to have comments and a specific order in their verification file and want to merge the diff by hand. It's also useful to avoid having to actually execute the build to check if all configurations would be ok.
Ignore trusted modules when writing the file This is particularly useful when you want to ignore some modules in the output file (for example, the native-platform snapshots) but don't want them to appear in the verification file either.
The checking is also slightly changed so that we would only check if a module is trusted if there's actually a verification error.