Configure on demand full understanding

[jraska]

Current plan

• Revert the #271 Fix loading projects and subprojects #272 change and release version 2.7.1 to come back to stable behaviour and not lose trust of the plugin users.
• Keep the 2.7.0 out for experimenting
• Get the full understanding without time pressure.
• Come up with final proposal - --no-configure-on-demand being mandatory is a likely option, but then I think it should be version 3.0.0 as quite breaking change.
• Related issues: Unable to generate a module graph #271 , Task 'assertModuleGraph' not found (v2.7.0) #277