Failure to parse Grizzly generated YAML

[malcolmholmes]

Grafana has the capacity to create some bizarre JSON. In two cases identified, this means Grizzly will create YAML that it cannot parse.

Those two scenarios where keys include newlines and where keys include backslashes.

For the usecase where we wish to download a whole Grafana instance, Grizzly failing to parse its own output is a real problem.

[malcolmholmes]

I've created a PR providing tests to the underlying YAML library: goccy/go-yaml#418

[malcolmholmes]

There is a workaround for this: you can now pull resources in JSON instead of YAML when this issue occurs.

[malcolmholmes]

Closing in lieu of #245