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

• PhpTestFrameworks.binaryPath/configFile always answer for the active profile, and since PHP for OpenIDE 0.9.7 the Testo binary and config can be set per profile. TestoLaunch reads the chosen profile's entry through PhpTestFrameworkSettings.resolved and PhpTestFrameworkDetector, which are @ApiStatus.Internal (the verifier reports them as internal API usages, still Compatible). Each call falls back to the public facade on a LinkageError.

• PHP for OpenIDE 0.9.4 publishes no way from a profile id to its launch environment: PhpLaunchEnvironments.of is Kotlin-internal, ProfileLaunchEnvironment is @ApiStatus.Internal, and PhpLaunchEnvironment.allOf(project) carries no ids. TestoRunConfiguration.profileEnvironment matches the saved id by position (active profile first, then the registry order), checks the display name, and refuses a list that does not line up. Worth asking upstream for a public lookup.

• 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

[roxblnfk]

Moved to #135: the branch now lives in this repository and targets open-ide, where the OpenIDE work continues.