Code actions and code lens don't display in config file when using JSONC file extension

[garrytrinder]

Describe the bug

When using the .jsonc file extension for Dev Proxy Toolkit configuration files, code actions and code lens features do not display. This behavior differs from .json files, where these features work as expected.

Expected behavior

.jsonc files should behave the same as .json files. Code actions and code lens should be available when editing configuration files with a .jsonc extension.

To Reproduce

1. Open a Dev Proxy Toolkit configuration file with a .jsonc extension (e.g., .devproxyrc.jsonc).
2. Observe that code actions and code lens features are not available.
3. Rename the file to use a .json extension (e.g., .devproxyrc.json).
4. Observe that code actions and code lens features work as expected.

Screenshot

Additional context

• This is a bug in Dev Proxy Toolkit.
• The .jsonc extension is useful for configuration files that contain comments and should be supported equivalently to .json.
• Please investigate and resolve the discrepancy in behavior between .jsonc and .json files.