fix: merge ports and ingress configs correctly in NetworkRuleConfig

Use `replace` patch merging strategy for `portSelector.ports` and `ingress`es in `NetworkRuleConfig` document, so that they do not have duplicate entries and/or fail on port range validation.

Closes #8136.

Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>

pkg/machinery/config/types/network/rule_config.go

@@ -55,7 +55,7 @@ type RuleConfigV1Alpha1 struct {
 	PortSelector RulePortSelector `yaml:"portSelector"`
 	//   description: |
 	//     Ingress defines which source subnets are allowed to access the host ports/protocols defined by the `portSelector`.
-	Ingress IngressConfig `yaml:"ingress"`
+	Ingress IngressConfig `yaml:"ingress" merge:"replace"`
 }
 
 // RulePortSelector is a port selector for the network rule.
@@ -68,7 +68,7 @@ type RulePortSelector struct {
 	//       examplePortRanges1()
 	//    - value: >
 	//       examplePortRanges2()
-	Ports PortRanges `yaml:"ports"`
+	Ports PortRanges `yaml:"ports" merge:"replace"`
 	//   description: |
 	//     Protocol defines traffic protocol (e.g. TCP or UDP).
 	//   values: