Item form discards user-entered scope when the subcontext feature is disabled
## Problem
Follow-up to:
#3586294+s
Parent:
#3586310+s
_**This issue should be verified prior to working on it to make sure it is valid.**_
This should be fixed here:
#3586218+s
`AiContextItemForm::buildEntity()` computes `$inherits_parent_scope = $entity->hasParent() && $entity->inheritsParentScope();` without checking `isSubcontextEnabled()`. With the feature toggled off, the "Same as parent" checkbox is not rendered and the scope widgets are fully visible — yet scope extraction is skipped and `target_entities` is cleared. `preSave()` then strips the parent, leaving a top-level item with empty scope: the user's entered values are silently dropped and the item becomes an unintended match-all candidate.
## Proposed resolution
Gate the check on the feature flag: `$this->isSubcontextEnabled() && $entity->hasParent() && $entity->inheritsParentScope()`. Add a functional test covering saving a child with the feature disabled.
## AI usage
- [x] AI assisted issue
issue