oav tool output of `oav validate-example` is not JSON
Issue Description
The output of invoking oav validate-example <filepath> -l json -f out.json is not a valid json.
For example: When running oav tool on the folder below: swagger.zip
oav validate-example swagger/specification/applications/resource-manager/Applications.Core/preview/2022-03-15-privatepreview/applications.json -l json -f out.json
See how the resutling values in out.json are not valid json by trying to consume this using jq

Additional Info
Valid json has double quoted properties and values and each object should be in a json array separated by commas.
@asilverman , JSON format isn't supported in output though the loglevel include it. Are you trying to access result by Jquery? I would like to know more about your using scenario.
Hi @raych1, my use case is that I would like to run oav tool in CI/CD and parse the output in a way that is parsable by a machine. Additionally if json is not suported then it shouldn't be included in loglevel...
In any case it should be simple enough to support JSON as an output and also conside that it is an industry standard.
To answer your question, yes I want to traverse the output messages using jquery