fix #89 Resolve the ui.default option with a normalizer (nested options removed in Symfony 8)

[njoubert-cleverage]

Description

Fixes #89.

ProcessConfigurationsManager resolves the ui.default option with a normalizer and its own OptionsResolver (as already done for ui), instead of nested options defined with setDefault() (deprecated since symfony/options-resolver 7.3, removed in 8.0). A single code path for Symfony 6.4, 7.4 and 8: setOptions() does not exist before 7.3.

The rules are unchanged: input defaults to null, context to [], each context item must be an array with the required key and value, unknown options are rejected.

Tests:

• ProcessConfigurationsManagerTest: default resolved to {input: null, context: []} when not configured, default without context, invalid values (not an array, unknown option, context not an array, item not an array, item without value, item with an unknown option)
• tests/App/config/packages.yaml: the default workaround of test.upload is removed, so LaunchActionTest::testLaunchWithFileUpload covers a launch form without ui.default (also asserts that no context row is displayed)

Checked:

• bundle (Symfony 8.1, PHP 8.5): 329 tests OK; without the fix, 9 of them fail (including the functional test, 500). PHPStan, PHP-CS-Fixer, Rector OK
• process-bundle-demo (Symfony 7.4): the 4 launch forms are displayed with their default values, and the "Defining nested options" deprecation is gone

Requirements

• Documentation updates
  • Reference
  • Changelog
• Unit tests

Breaking changes

None: the Symfony 7.x behaviour is restored with Symfony 8 (only the wording of the validation error messages changes).

🤖 Generated with Claude Code