Support multiple `resource_type` for terraform_plan provider operations

• All operator '*' is possible for the resource_type
• Multiselector (multiple types) can be selected for the resource_type

e.g.

{
  "evaluators": [
    {
      "description": "VPC needs to have one tag with key:'costcenter' and any value ",
      "condition": {
        "type": "IsNotEmpty",
        "value": "",
        "error_tolerance": 1
      },
      "id": "eval-id-1",
      "provider_args": {
        "operation_type": "attribute",
        "terraform_resource_attribute": "tags.costcenter",
        "terraform_resource_type": "*"
      }
    },
    {
      "id": "eval-id-2",
      "description": "",
      "provider_args": {
        "operation_type": "action",
        "terraform_resource_type": ["aws_vpc", "aws_ec2"]
      },
      "condition": {
        "type": "Equals",
        "value": "create",
        "error_tolerance": 1
      }
    }
  ],
  "meta": {
    "required_provider": "stackguardian/terraform_plan",
    "version": "v1"
  },
  "eval_expression": "eval-id-1 || eval-id-2"
}

Start at the terraform_plan provider operation handling and trace how provider_args parses terraform_resource_type for attribute and action operations. Done means both the '*' wildcard and a list of resource types, such as ["aws_vpc", "aws_ec2"], are accepted and evaluated as specified.