Double-clicking on config file errors should take you to the config file

**Bicep version**
Latest in `main`

**Describe the bug**
Double-clicking on config file errors should take you to the config file instead of the broken bicep file.

**To Reproduce**
1. Create or update bicepconfig.json to have empty content.
2. Open a bicep file.
3. An error like the following should appear:
4. Double click on the error in VS code.

Expected behavior: VS code takes you to the broken config file. (Ideally, the location that is malformed in the config file.)
Actual behavior: VS code will take you to the Bicep file that attempted to consume the config file.

**Additional context**
This may very well be difficult to implement without a proper JSON language server support.

Reproduce the problem with an empty bicepconfig.json and an open Bicep file in VS Code. Trace the diagnostic's navigation target and ensure double-clicking the config error opens bicepconfig.json, ideally at the malformed location, rather than the consuming Bicep file.

Written by the indexing model from the issue text.