Although `TestPlan` exposes an `add(TestIdentifier)` method, it was only
ever intended for internal use by JUnit's `DefaultLauncher` which
already adds dynamic test identifiers to the `TestPlan`. The JUnit team
is going to make the `add()` throw an exception on modifications from
listeners. Thus, this commit removes the unnecessary call.

Render `project default` interpreter in the same way as other interpreters in run configuration settings (PY-32814)

don't capture potentially-changing MethodData in PsiMethod-bound cached value (EA-122934, EA-132920)

to simplify testing

completion: don't Tab-overwrite in read-only part of injected file (EA-116414 - assert: DocumentWindowImpl.deleteString)

Follow-up to bbebd174

Inlining action: show conflicts when replacing variable with variable that might change (IDEA-204546)

Inlining action: show conflict if replacement variable changes before last read of original variable (IDEA-204546)