feat(openide): lay the run configuration out like PhpStorm's, with its own interpreter

[roxblnfk]

What was changed

• The OpenIDE run configuration form follows the PHPUnit one: Test Runner with the scope as radio buttons and only that scope's fields, then Command Line — Interpreter, Interpreter options, Testo executable, working directory, environment — then the Testo options (Filter, Reports, Coverage, Mutation Testing).
• Each configuration has its own PHP interpreter; empty means the project default, so existing configurations keep following the active profile. A deleted profile fails the configuration check and the run instead of falling back. Every launch path resolves it: run, debug, coverage, mutation, Rerun Failed Tests and Infection's tool environment.
• Interpreter options go right after php, before the plugin's own debug / PCOV options.
• The Command field is gone; a saved command still loads and runs, as on PhpStorm.
• The Filter tags are labelled Suites / Groups / Exclude groups, no longer clashing with the Suite scope.
• The Type filter is a tag list on both PhpStorm and OpenIDE, one --type per tag (Testo ORs them, !name excludes). A single type saved by earlier builds is folded into the list on load.

Review notes

• The interpreter is resolved through PHP for OpenIDE 0.9.8's profile API: PhpLaunchEnvironment.of(project, profileId) for the environment and the profileId overloads of PhpTestFrameworks.binaryPath/configFile for the Testo binary and config. The overloads without an id answer for the active profile whatever the configuration names, and the ones with it return null for a profile missing from PhpInterpreterRegistry.
• Not done: interpreter options do not reach the Testo process Infection spawns; the shared options panel stays per implementation (the PhpStorm editor wraps the PHP plugin's form and works on TestoRunnerSettings).

Checklist

• Closes OpenIDE: align the run configuration form with PhpStorm's (interpreter field, no Command field) #129
• How was this tested:
  • Unit tests added (TestoInterpreterTest: legacy configurations, saved interpreter, deleted profile, position matching, form round-trip)
  • buildPlugin verifyPlugin -PphpApi=openide locally (Compatible)
  • check green locally — on Windows 15 OpenIDE and 10 PhpStorm tests fail on path separators, the same set as earlier runs on main (On Windows, a class run is never recognised as the configuration of its context #120, Behaviour baselines fail on Windows and do not cover remote interpreters, clones or Debug runs #122); Ubuntu CI is the reference
  • Tested manually in OpenIDE

Replaces #130, which targeted main.

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2026.2.2
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions