Refactoring for the constructors

[ufechner7]

The constructors for Solver and Wings should use VSMSettings as first parameter.

• Add the VSMSettings struct
• Use it for creating Wings
• Use it for creating Solver
• Fix the tests
• Fix the examples
• Fix the documentation

Not sure if BodyAerodynamics should also needs it.

[jellepoland]

I adjusted the script, that now uses the settings like:

# Create wing, body_aero, and solver objects using settings
wing = YamlWing(settings.wings[1].yaml_path; 
    n_panels=settings.wings[1].n_panels, 
    n_groups=settings.wings[1].n_groups,
    spanwise_distribution=settings.wings[1].spanwise_panel_distribution
)
body_aero = BodyAerodynamics([wing])
solver = Solver(body_aero;
    aerodynamic_model_type=settings.solver_settings.aerodynamic_model_type,
    density=settings.solver_settings.density,
    max_iterations=settings.solver_settings.max_iterations,
    rtol=settings.solver_settings.rtol,
    relaxation_factor=settings.solver_settings.relaxation_factor,
    core_radius_fraction=settings.solver_settings.core_radius_fraction,
)
# Set flight conditions
α = deg2rad(settings.condition.alpha)
β = deg2rad(settings.condition.beta)
va = settings.condition.wind_speed * [
    cos(α)*cos(β),  # X_b (forward)
    sin(β),         # Y_b (right)
    sin(α)*cos(β)   # Z_b (down)
]
set_va!(body_aero, va)
# Run the solver
results = VortexStepMethod.solve(solver, body_aero; log=true)

This still feels a bit verbose, as one could also only parse settings into YamlWing() and Solver(), but I decided not to change this as this would break other code usage...

To make it possible to run the script, fully documented in yaml files, I adjusted the YAML and settings.jl accordingly

[1-Bart-1]

This still feels a bit verbose, as one could also only parse settings into YamlWing() and Solver(), but I decided not to change this as this would break other code usage...

Please change it to just parsing settings
wing = YamlWing(settings;
It is ok to adjust other code, because this is better and easier to use. If something is an improvement, you should implement it. If it is a breaking change (the user interface changes), we release the update as a breaking change.