connect: fix shouldPersistNewRootAndConfig logic

hashicorp#12298 introduced an improvement
to prevent raft commit for no-op operations, but while moving conditions
into a function, author inversed the logic while keep same boolean
operations. As a consequence, this prevents one to update provider config
of a secondary CA.
Correct code was suggested in a review comment anyway, so apply it:
hashicorp#12298 (review)

agent/consul/leader_connect_ca.go

@@ -754,7 +754,7 @@ func shouldPersistNewRootAndConfig(newActiveRoot *structs.CARoot, oldConfig, new
 	if newConfig == nil {
 		return false
 	}
-	return newConfig.Provider == oldConfig.Provider && reflect.DeepEqual(newConfig.Config, oldConfig.Config)
+	return newConfig.Provider != oldConfig.Provider || !reflect.DeepEqual(newConfig.Config, oldConfig.Config)
 }
 
 func (c *CAManager) UpdateConfiguration(args *structs.CARequest) (reterr error) {