Expand definition of `jupiterone_rule.operations`

[asaba-hashi]

Problem to Solve

Operations are currently represented in the HCL as a single JSON document that is marshalled into complex types. This combined with ids that are generated on creation make it difficult to keep the state consistent with values read from the serer which can result in spurious differences being reported.

Proposed Changed

Add operations as it's own list such that it each operation can be specified itself, but still support copy/paste from the J1 UI using jsonencode.

  operations = [
    {
      when = jsonencode({
        "type" : "FILTER",
        "specVersion" : 1,
        "condition" : [
          "AND",
          [
            "queries.query0.total",
            "<",
            1000
          ]
        ]
      }),
      actions = [
        jsonencode({
          "targetValue" : "INFO",
          "type" : "SET_PROPERTY",
          "targetProperty" : "alertLevel"
        }),
        jsonencode({
          "type" : "CREATE_ALERT"
        })
      ]
    }
  ]

This will be a breaking change from 0.5.0:

1. JSON strings/heredocs must be changed to jsonencode blocks.
2. Likely some other smaller changes will be necessary for the current alert schema.

[asaba-hashi]

The HCL/jsonencode/decode is not as flexible as I hoped, so the POC in #143 breaks operations down to where the JSON type is specified by the API. I think this level is a workable compromise between being able to copy configured actions out of the UI/API with some manual work and being able to reuse/recompose actions in terraform.