Inconsistent order of calling update_defaults_from_yaml() across classes

[kimpaller]

Inconsistent order of calling update_defaults_from_yaml() during initiation across classes. This leaves the question of who decides the final value of a class field, nebula-config or user-supplied argument?