Skip configuration "include" nodes when file is empty
Whenever the yaml file has an "include" key, suricata include the value as a new configuration file.
If the included file is empty suricata will create a node with an empty string as a name. This should be avoided.
Note that this only happens if the included file is a valid empty yaml file (i.e, starting with "%YAML 1.1\n---\n" sequence).
It is sufficient to skip an included file whenever it's empty (value0 == '\0').