Adds account level and workspace level operations for ngwaf rules using json file inputs

[anthony-gomez-fastly]

Change summary

Add support for NGWAF rule manipulation. create and update are handled by allowing the user to proved a valid json that can be unmarshalled to the matching structure for the given rule level.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

• Does your submission pass tests?

Changes to Core Features:

• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

[rcaril]

When I did some testing with a simple rule payload, a rule was created with no issues. However, when I attempted to use a more complex payload that contained several group operators, some nested fields were mapped as null.

I used this arbitrary payload:

{
    "type": "request",
    "description": "complex_test",
    "enabled": true,
    "expires_at": "",
    "group_operator": "all",
    "conditions": [
        {
            "type": "single",
            "field": "ip",
            "operator": "equals",
            "value": "1.2.3.4"
        },
        {
            "type": "single",
            "field": "country",
            "operator": "equals",
            "value": "AE"
        },
        {
            "type": "group",
            "group_operator": "all",
            "conditions": [
                {
                    "type": "single",
                    "field": "ip",
                    "operator": "equals",
                    "value": "2.4.5.6"
                },
                {
                    "type": "single",
                    "field": "country",
                    "operator": "equals",
                    "value": "AD"
                }
            ]
        },
        {
            "type": "group",
            "group_operator": "all",
            "conditions": [
                {
                    "type": "single",
                    "field": "domain",
                    "operator": "equals",
                    "value": "test.com"
                },
                {
                    "type": "single",
                    "field": "agent_name",
                    "operator": "equals",
                    "value": "test"
                }
            ]
        }
    ],
    "actions": [
        {
            "type": "browser_challenge",
            "allow_interactive": true,
            "signal": ""
        }
    ],
    "request_logging": "none"
}

The following was sent to the API, which resulted in an error.

{
      "actions": [
          {
              "allow_interactive": true,
              "signal": "",
              "type": "browser_challenge"
          }
      ],
      "conditions": [
          {
              "type": "single",
              "field": "ip",
              "operator": "equals",
              "value": "1.2.3.4"
          },
          {
              "type": "single",
              "field": "country",
              "operator": "equals",
              "value": "AE"
          },
          {
              "type": "single",
              "field": null,
              "operator": null,
              "value": null
          },
          {
              "type": "single",
              "field": null,
              "operator": null,
              "value": null
          }
      ],
      "description": "complex_test",
      "enabled": true,
      "scope": {
          "type": "workspace",
          "applies_to": ["nBw2ENWfOY1M2dpSwK1l5R"]
      },
      "type": "request"
  }

You can see here that some fields were not parsed correctly. I believe we need to do some custom unmarshaling here to handle the group conditions.

[rcaril]

I think we need to map top level "type": "group", to GroupConditions in go-fastly and top level "type": "single", to Condiitons.

[anthony-gomez-fastly]

ah rats, i'll get on that. TY!