Search results order

[mkundu1]

>> search("boundary", match_whole_word=True) 
<solver_session>.setup.boundary_conditions.exhaust_fan["<name>"].phase["<name>"].structure.x_disp_boundary_condition (Parameter)
<solver_session>.setup.boundary_conditions.exhaust_fan["<name>"].structure.x_disp_boundary_condition (Parameter)
<solver_session>.setup.boundary_conditions.inlet_vent["<name>"].phase["<name>"].structure.x_disp_boundary_condition (Parameter)
<solver_session>.setup.boundary_conditions.inlet_vent["<name>"].structure.x_disp_boundary_condition (Parameter)
...
<solver_session>.setup.boundary_conditions

The path <solver_session>.setup.boundary_conditions should be shown above the child-paths.

Ideally, the search results should be presented in a breadth-first order of the settings tree. But the above issue can be fixed independently.