Settings UI shows no warning (and possibly an incorrect value) when an invalid enum is in settings.json

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions --> <!-- 🔎 Search existing issues to avoid creating duplicates. --> <!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ --> <!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --> <!-- 🔧 Launch with `code --disable-extensions` to check. --> Does this issue occur when all extensions are disabled?: Yes <!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --> <!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. --> - VS Code Version:Version: 1.72.0-insider (user setup) Commit: 9fb452c4852ef098206ec67a2b236ad5fd0ba828 Date: 2022-10-03T07:34:58.711Z Electron: 19.0.17 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0.22621 Sandboxed: Yes Steps to Reproduce: 1. Install the C/C++ extension version 1.13.1 (pre-release). 2. Add the invalid/deprecated setting "C_Cpp.enhancedColorization": "Disabled" to settings.json (the enum was renamed "disabled". 3. View the settings UI. NOTE: The bug is probably reproduceable with some other setting enum, but I haven't tried. Bug: No warning appears in the settings UI, and it shows the misleading/unused default value of "enabled" -- our extension still handles the "Disabled" value for backwards compatibility, so the UI settings misleading shows the wrong value. This can confuse users into believing the setting is actually enabled and there's a bug causing it to not work, when in fact if they opened the settings.json …