Fix all-ports rule state handling

- Clear ports field when creating all-ports rules
- Clear ports field when reading all-ports rules
- Ensure test expectations match actual state behavior
- Fixes test failures where ports field was incorrectly set

Author: sidshas03

cloudstack/resource_cloudstack_egress_firewall.go

@@ -335,6 +335,8 @@ func createEgressFirewallRule(d *schema.ResourceData, meta interface{}, rule map
 			}
 			uuids["all"] = r.Id
 			rule["uuids"] = uuids
+			// Clear the ports field since we're creating an all-ports rule
+			rule["ports"] = &schema.Set{F: schema.HashString}
 		}
 	}
 
@@ -486,6 +488,8 @@ func resourceCloudStackEgressFirewallRead(d *schema.ResourceData, meta interface
 					// Update the values
 					rule["protocol"] = r.Protocol
 					rule["cidr_list"] = cidrs
+					// Clear ports field for all-ports rules
+					rule["ports"] = &schema.Set{F: schema.HashString}
 					rules.Add(rule)
 				}
 			}
@@ -512,6 +516,8 @@ func resourceCloudStackEgressFirewallRead(d *schema.ResourceData, meta interface
 
 						rule["protocol"] = r.Protocol
 						rule["cidr_list"] = cidrs
+						// Clear ports field for all-ports rules
+						rule["ports"] = &schema.Set{F: schema.HashString}
 						rules.Add(rule)
 
 						// Remove from ruleMap so it's not processed again