Error parsing some custom metadata annotation

[anderseknert]

@garethahealy reported that Regal v0.26.1 fails to process policies with some particular custom metadata annotations.

Example:

p.rego

# METADATA
# custom:
#   matchers:
#     kinds:
#     - apiGroups:
#       - osb.openshift.io
#       kinds:
#       - AutomationBroker
#       - TemplateServiceBroker
#   skipConstraint: true
package ocp.deprecated.ocp4_2.osb_v1

regal lint p.rego
error(s) encountered while linting: failed to lint using Rego rules: error encountered in rule evaluation failed preparing AST: JSON rountrip failed for module: ReadMapCB: object not ended with }, error found in #10 byte of ...|":null}]}"skipConstr|..., bigger context ...|ustom":{"matchers":{"kinds":[{"apiGroups":null}]}"skipConstraint":true}}],"comments":[{"location":"1|...

OPA doesn't seem to have any issues with the same file.

[anderseknert]

This bug is in the new roast JSON encoder, where multiple key/value-pairs in the custom object wasn't properly separated by commas. It thought we had got a fairly good coverage just by serializing all 200+ Rego files in the Regal repo... but it turns out we never have 2+ custom attributes in any metadata here 🤦

Fixed in StyraInc/roast#3 ... as soon as that's merged, I'll push a new tag and will bump the dependency for v0.26.2