Merge identical nodes instead of ignoring some, clarify handling in docs

[eugenesvk]

Suppose, for purely config organizational purposes, I wanted to have a config with identical domains defined multiple times:

 // set up TLS for various domains first
domain.com  {auto_tls_challenge "dns-01" provider="X" api_key="Y"}
example.com {auto_tls_challenge "dns-01" provider="X" api_key="Y"}

// more configs

// set up "cleaner" actual connections
domain.com  {proxy "http://localhost:8080"}
example.com {proxy "http://localhost:9090"}

How does Ferron handle those? Does it consolidate the configs or overwrite them, letting the last one win? Ignoring the last one?

Seems like the last method is used, but why? I think it'd be better if you had the flexibility described above and the nodes were merged instead, with only identical elements being overwritten (so, last one wins) as it seems more 'logical' following the document flow

Also would be nice to document explicitly how duplicate nodes are handled

[DorianNiemiecSVRJS]

I tried this Ferron configuration:

// set up TLS for various domains first
domain.com  {auto_tls #false}
example.com {auto_tls #false}

// more configs

// set up "cleaner" actual connections
domain.com  {proxy "http://localhost:8080"}
example.com {proxy "http://localhost:9090"}

And using Ferron built from the development branch (develop-2.x), it seems like the node merging works correctly...

[eugenesvk]

Hm, the ones I was testing with v2.6.0 were:

"IPv4:80,IPv6:80"  {
  status 404
}
"IPv4:80,IPv6:80" {
  status 403
}

And always got the first one 404, so the second one is ignored instead of overriding the first one