fix: remove invalid MaxItems constraint from Okta ML policy

Remove MaxItems: 1 from rule field in both resource and data source. MaxItems cannot be used on computed-only fields in data sources and was causing provider validation errors. Aligns with AWS ML policy implementation pattern.

Author: harshampatel-sysdig

sysdig/data_source_sysdig_secure_okta_ml_policy.go

@@ -45,7 +45,6 @@ func createOktaMLPolicyDataSourceSchema() map[string]*schema.Schema {
 		"rule": {
 			Type:     schema.TypeList,
 			Computed: true,
-			MaxItems: 1,
 			Elem: &schema.Resource{
 				Schema: map[string]*schema.Schema{
 					"id":                      ReadOnlyIntSchema(),

sysdig/resource_sysdig_secure_okta_ml_policy.go

@@ -54,7 +54,6 @@ func resourceSysdigSecureOktaMLPolicy() *schema.Resource {
 			"rule": {
 				Type:     schema.TypeList,
 				Required: true,
-				MaxItems: 1,
 				Elem: &schema.Resource{
 					Schema: map[string]*schema.Schema{
 						"id":   ReadOnlyIntSchema(),