Unusable error diagnostics output on broken config

[shoffmeister]

Describe the bug

Provided with an imperfect ruleset specification (.spectral.yaml), the vscode extension diagnostic output is unusable for actually diagnosing the problem.

To Reproduce

Drop a bad ruleset specification into a workspace which has any OpenAPI specs, e.g.

extends: spectral:oas

overrides:
  wombats:

Open the OpenAPI specs document to force revalidation.

Expected behavior

Reasonably helpful error output.

Actual behaviour

"Spectral: An error occurred while validating . Please see the 'Spectral' output channel for details."

Fair enough, but that output channel then has

[Error - 8:38:27 AM] An error occurred while validating document <document>:
Unable to read ruleset at ../.spectral.yaml. 
AggregateError

AggregateError is not helpful at all, as this ... aggregates the real errors. And the real errors are not shown anywhere.

npx spectral lint <document> --verbose will show a lot more detail - but then I am using the vscode extension for a reason ;)

Please, when there is an exception or an AggregateError emit the complete error context.

[shoffmeister]

FWIW, this is only about the technical production of vscode error output - not the content of the error message emitted by the validator itself.