Fix FunctionalJavascript test failures on 1.4.x introduced by MDX editor Drupal.behavior conversion
## Summary
FunctionalJavascript tests that fill in a prompt field all fail with `WebDriver\Exception\ElementNotInteractable` on the `1.4.x` branch. Commit [`be77241c`](https://git.drupalcode.org/project/ai/-/commit/be77241c9486bc07d800e2e2fe8ab41600e09d29) converted the MDX editor from a one-time `DOMContentLoaded` init to a `Drupal.behavior`, which now runs after every AJAX response and hides the underlying `<textarea>` with `display:none`. Tests were calling `fillField()` directly on that hidden element. The `1.3.x` branch is not affected as it does not contain this commit.
## Steps to reproduce
1. Check out the `1.4.x` branch
2. Create a tag (e.g. `1.4.2`) to trigger the FunctionalJavascript pipeline
3. Observe failures in `AiPromptElementTest` and `AiPromptElementNestingTest`
## Expected result
All FunctionalJavascript tests pass. The prompt field is filled programmatically via the `drupal:mdx-fill` custom event that the MDX editor already listens for.
## Actual result
Tests throw `WebDriver\Exception\ElementNotInteractable` when attempting to fill the prompt textarea. The MDX editor has hidden the textarea and replaced it with a React rich-text editor after the AJAX response. Selenium cannot interact with a `display:none` element.
Failing tests:
- `AiPromptElementTest::testAiPromptElementUi`
- `AiPromptElementTest::testAiPromptElementAccess`
- `AiPromptElementNestingTest::testRootLevelPromptCreationFlow`
- `AiPromptElementNestingTest::testSubformNestedPromptCreationFlow`
- `AiPromptElementNestingTest::testSubformNestedDuplicateMachineNameRejected`
- `AiPromptElementNestingTest::testSubformStatePromptCreationFlow`
## Fix
1. **Test instrumentation** — Add a `fillMdxEditorField()` helper to `BaseClassFunctionalJavascriptTests` that dispatches the `drupal:mdx-fill` custom event instead of calling `fillField()` on the hidden textarea. Replace all affected `fillField()` calls in `AiPromptElementTest` and `AiPromptElementNestingTest`.
2. **Drupal 11.3 deprecation** — Add `#[RunTestsInSeparateProcesses]` to all 4 FunctionalJavascript test classes (`AiPromptElementTest`, `AiPromptElementNestingTest`, `AiProviderConfigurationElementTest`, `AiProviderConfigurationElementNestingTest`). Required since Drupal 11.3, becomes a hard error in Drupal 12. Also add missing `declare(strict_types=1)` to `AiPromptElementTest`.
## Environment
- Drupal version: 11.x
- Module version: 1.4.x (not present on 1.3.x)
- PHP version: 8.4
- Provider: n/a (test-only fix)
- Last known working version: 1.4.1 (before commit `be77241c`)
### Error messages or logs
```
WebDriver\Exception\ElementNotInteractable: Element is not reachable by keyboard
at tests/src/FunctionalJavascript/AiPromptElementTest.php
at tests/src/FunctionalJavascript/AiPromptElementNestingTest.php
```
<!-- If this issue description was significantly AI-generated (entire sections, not autocomplete), please note it in a comment below. See https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquette/policy-on-the-use-of-ai-when-contributing-to-drupal -->
<!-- /label ~"aiCoreModule" -->
issue