Harsh error behavior with bicepconfig.json files with unexpected types

# Repro 1
## bicepconfig.json
```json
{
"analyzers": "whoops"
}
```
## main.bicep
```bicep
param test string = 'abc'
```
Hover over param 'test' definition
!)

# Repro 2
Use this bicepconfig.json file:
```json
{
"analyzers": {
"core": {
"rules": {
"no-unused-params": {
"level": {
}
}
}
}
}
}
```
You get similar behavior
# Repro 3
The same happens from the command line:

# NOTE
Malformed JSON is handled better:
## bicepconfig.json
```json
{
```
gives

Start by reproducing the three cases using the bicepconfig.json and main.bicep examples, both through parameter hover and the command line. Compare unexpected JSON types with the existing malformed-JSON handling. Done means invalid configuration types produce a useful diagnostic or graceful error instead of the harsh behavior shown in the issue.

Written by the indexing model from the issue text.