objects can be created. Transfer squantities not ok

Boundary layer results can be saved in vtk format. Correctly handle inputs fuselage for fuselage and added fuselage type in c++ classes

Now the viscous solver is created after the interface. This allows less user inputs and avoids conflict between parameters. The blSolverInterface class was reworked and documentation was improved. The sections can now have no wake or only one side (for fuselage for example). Bug fix here and there and ajusted tests. Only the onera validation case is up to date.

The data structures of the viscous solver have been reworked to avoid lists of lists of lists... Users now have the possibility to automatically generate sections on wing or to use prescribed section from another mesh. First option requires to identified upper and lower sides and this information is also used by the rbf interpolator.

Modified file include accordingly

 - Revert default value of span. - Removed api test for 3D because it could lead to issues when ctests run in parallel (tests would open the same files at the same time which would cause high latency. - Fixed values of Rae 3D case wrt to previous fix

Plus fixed a bug that would set span to 0

New surface mesh is imposed in the viscous solver in 2D and stagnation point is recomputed at the first coupling iteration

Added adjoint for AoA and mesh in 2D. Nodes indices are now passed to the BoundaryLayer object

Boundary layer c++ objects are created in python with swig and are manipulated by the interface. The initial condition of the viscous solver was changed. All test cases have been adapted. A decrease in the number of iterations is globally observed. Results are slightly improved especially for the RAE validation case.

Driver now computes the average position of the transition

Added vtk support in Dart api. Modified writing of boundary layer slices and introduced new argument of blast - writeSlices - which indicates vtk where to extract cps. The feature is not yet available for the boundary layer slices as this would require interpolation in the viscous solver.

Fixed API, dart interface and prevented segfault if the number of sections is not imposed correctly.

Contains 2D and 3D developements as well as the api.