ProtectedhidingRe-entrancy guard: PreferenceSchemaService.updateSchemaProperty fires onDidChangeSchema
synchronously, so our own writes call hideAiPreferences back while it is still iterating
the service's live property map.
ProtectedhideTurns on hidden for every ai-features.* property that is not already hidden. Idempotent, so it
can run on every schema change. The hidden check and hiding each independently stop our own
updates from looping; keep both, since dropping either leaves the pass one edit away from recursing.
Allows to do additional intialisation of the preference schema, for example registering overrides
the preference schema service
Hides all AI preferences (
ai-features.*) from the Settings UI once the AI Configuration view covers them (eclipsesource/theia#316). The schemas stay registered so validation and typing are unaffected; only their Settings-UI visibility is turned off viahidden: true. Matching by prefix means any future AI preference is covered without per-schema maintenance.