`cucumber.parameterTypes` changes unrecognised until feature file is re-opened

### 👓 What did you see?

When on a file that is reporting an undefined step due to a misconfigured `cucumber.parameterTypes` value, when that value is changed, the undefined step error remains until the file is closed and re-opened.

### ✅ What did you expect to see?

After changing `cucumber.parameterTypes`, feature files should immediately check for errors and update accordingly.

### 📦 Which tool/library version are you using?

- node v25.2.1
- cucumber/vscode v1.11.0
- cucumber-js v11.3.0

### 🔬 How could we reproduce it?

1. Add `{ "name": "array", "regexp": "/\\[.*\\]/" }` to `.vscode/settings.json` `cucumber.parameterTypes`.
2. Create the step `Array {array} has length 0`.
3. Create a feature file with step `Array [] has length 0`. This will create an undefined step error because the regular expression is incorrect.
4. Change the regular expression to `"\\[.*\\]"` while the feature file is open in a separate view. While the regular expression is now correct, the undefined step error will remain.
5. Close the feature file and re-open it. The undefined step error will now disappear.

### 📚 Any additional context?

_No response_