`editor.inlineSuggest.edits.enabled` gates NES but is not registered in the configuration schema

- VS Code Version: 1.132.0 (built from source, `3ddd267c500`)
- OS Version: macOS 26.5.2

## Problem

`editor.inlineSuggest.edits.enabled` is the master switch that gates whether next edit suggestions render at all, but it is never registered in the configuration schema.

It is validated:

```ts
// src/vs/editor/common/config/editorOptions.ts (_validateEdits)
enabled: boolean(input.enabled, this.defaultValue.edits.enabled),
```

and consumed:

```ts
// src/vs/editor/contrib/inlineCompletions/browser/model/inlineCompletionsModel.ts
this._inlineEditsEnabled = inlineSuggest.map(v => !!v.edits.enabled);
```

but the schema object next to it only registers `edits.allowCodeShifting`, `edits.showLongDistanceHint`, `edits.longDistanceHintContextLineCount`, `edits.renderSideBySide` and `edits.showCollapsed`. There is no `'editor.inlineSuggest.edits.enabled'` entry.

## Steps to Reproduce

1. Search the Settings UI for `editor.inlineSuggest.edits.enabled` — nothing is found.
2. Add `"editor.inlineSuggest.edits.enabled": false` to `settings.json` — it is reported as an unknown configuration setting.
3. Trigger an edit that would normally produce a next edit suggestion.

## Actual

NES is fully suppressed — the setting **does** take effect, despite being unregistered and flagged as unknown. Verified live: with the setting applied, an edit that reliably produced a suggestion no longer produced one.

So it is a working kill switch that users cannot discover and that the editor warns about if they do find it.

## Expected

Either register it properly (with a description and the `nextEditSuggestions` tag, matching its five siblings), or, if NES enablement is meant to be owned solely by `github.copilot.nextEditSuggestions.enabled`, drop `enabled` from the `edits` options so there is a single source of truth.