-fdiagnostics-as-json does not handle error message from pre-processors
## Summary
GHC parses errors from pre-processors and `-ddump-json` convert them to JSON records:
```console
$ cat Foo.hs
{-# OPTIONS_GHC -F -pgmF ./pp.sh #-}
```
```console
$ cat pp.sh
#!/bin/bash
echo "Foo.hs:4:7:some error"
exit 1
```
```console
$ ghc -fno-code -ddump-json Foo.hs | head -n 2 | tail -n1 | json2yaml
span:
file: Foo.hs
startLine: 4
startCol: 7
endLine: 4
endCol: 7
messageClass: MCDiagnostic SevError ErrorWithoutFlag Nothing
doc: some error
```
In contrast, with `-fdiagnostics-as-json` GHC still parses the error messages, but they are not converted to JSON records.
## Steps to reproduce
```console
$ ghc -fno-code -fdiagnostics-as-json Foo.hs
Foo.hs:4:7: error: some error
...
```
(Note that GHC still parses the error message, and then pretty-prints it, as can be seen from the addition of `error: ` in between the location and the message. However, the error message is not converted to JSON.)
## Expected behavior
`-fdiagnostics-as-json` converts error messages from pre-processors to JSON, similar to what `-ddump-json` does.
## Environment
* GHC version used: 9.10.1
issue