file based indices: remove redundant isContentPhysical check (because it's equivalent to in memory mode flag)

This reverts commit 33877b0b

Info.plist is required for building macOS Launcher by the TC configuration:

https://buildserver.labs.intellij.net/viewLog.html?buildId=43643072&buildTypeId=ijplatform_master_Idea_MacLauncher&tab=buildLog&_focus=441

because it is a top-level module where Kotlin is allowed

idea.prepare.app.start.parallel is true by default only on macOS until HiDPI issue is not fixed on Linux

https://buildserver.labs.intellij.net/viewLog.html?buildId=43504729&tab=buildResultsDiv&buildTypeId=ijplatform_master_WebStorm_JavaScriptDebuggerTests_MacOS#testNameId-6648540928441028875

Found leaked class com.intellij.openapi.project.impl.ProjectImpl: Project (Disposed) express-generator; hash: 1725098648; place: Project (Disposed) express-generator
via 'com.intellij.terminal.JBTerminalWidget.myProject'; Value: 'Project (Disposed) express-generator' of class com.intellij.openapi.project.impl.ProjectImpl
via 'com.jediterm.terminal.ui.JediTermWidget$EmulatorTask.this$0'; Value: 'com.intellij.terminal.TerminalExecutionConsole$ConsoleTerminalWidget[terminal,0,0,0x0,invalid,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,prefe...' of class com.intellij.terminal.TerminalExecutionConsole$ConsoleTerminalWidget
via 'java.lang.Thread.target'; Value: 'com.jediterm.terminal.ui.JediTermWidget$EmulatorTask@18137d5' of class com.jediterm.terminal.ui.JediTermWidget$EmulatorTask
via '?'; Value: 'Thread[Connector-TtyConnector:/opt/buildAgent/temp/buildTmp/NodeJsTest_8.12.0/node-v8.12.0-darwin-x64/bin/node /opt/buildAgent/temp/buildTmp/NodeJsTest_8.12.0/node-v8.12.0-darwin-x64/lib/node_modules/...' of class java.lang.Thread
via 'java.lang.ThreadGroup.threads'; Value: '[Ljava.lang.Thread;@5508c719' of class [Ljava.lang.Thread;
via 'java.awt.EventQueue.threadGroup'; Value: 'java.lang.ThreadGroup[name=main,maxpri=10]' of class java.lang.ThreadGroup
via '?'; Value: 'com.intellij.ide.IdeEventQueue@7555782c' of class com.intellij.ide.IdeEventQueue
 (from IdeEventQueue.getInstance())

Java: Intention that wraps list/set/map with Collections.unmodifiable - don't suggest on the left-hand side of assignment (IDEA-208885)

util: move suspicious rethrow and rethrowAllAsUnchecked back from ExceptionUtilRt to ExceptionUtil (IDEA-CR-35889)

With maven-build-helper, one can define multiple executions that can
each add source or resource folders to the project. With the current
implementation, IntelliJ only considers the very first execution that
matches the given maven goal, like add-sources. However, it is perfectly
fine with Maven to define multiple executions with the same goal. This
also happens automatically, for example when multiple Maven profiles are
defined and active, that each call add-source of the maven-build-helper.

With this commit, I changed the folder importing strategy, so that not
only the first matching execution is considered, but all executions that
call the appropriate Maven goal.

I also added a test case that fails on current master, but passes with
this commit. It simulates a project structure with multiple additional
sources and resources folders, with each of them added in different
executions of the maven-build-helper. This can be a common scenario if
one extensively uses Maven profiles to trigger specific actions.