Provide a mechanism to exclude building specific modules in parallel

This could be very handy in case you have integration tests modules that do share some external resource.
This would require some kind of lock exclusion, similar to the junit annotation https://junit.org/junit5/docs/5.7.2/api/org.junit.jupiter.api/org/junit/jupiter/api/parallel/ResourceLock.html . However, I think we may have several forked JVMs in parallel in these cases, so a simple lock would not work...
A simple workaround would be add some dependencies at test scope between the ITs so that they're never executed in parallel, but that's not as clean.

Review the current parallel module scheduling and forked JVM behavior, focusing on how integration-test modules are selected and executed. Compare the proposed resource-lock approach with test-scope dependency ordering; done means a documented mechanism can prevent selected modules sharing an external resource from running concurrently across forked JVMs.

Written by the indexing model from the issue text.