feat: Improve error message when targetting wrong solver

[arng40]

This PR aim to improve the error message when a coupled solver target wrong solver

Before :

***** LOCATION: path/to/physicsSolvers/multiphysics/CoupledSolver.hpp:89
***** Controlling expression (should be false): solver == nullptr
***** Rank 0: coupledFlowAndWells (isothm_mass_inj_table.xml, l.5): Could not find solver 'comp' of type geos::CompositionalMultiphaseBase

After :

***** LOCATION: path/to/physicsSolvers/multiphysics/CoupledSolver.hpp:118
***** Controlling expression (should be false): true
***** Rank 0: coupledFlowAndWells (isothm_mass_inj_table.xml, l.5): Could not find solver  named 'comp'.
Available flow solvers are [ compflow ].

** StackTrace of 7 frames **`

if we don"t have any flow solver we get :

***** LOCATION: path/to/physicsSolvers/multiphysics/CoupledSolver.hpp:118
***** Controlling expression (should be false): true
***** Rank 0: coupledFlowAndWells (isothm_mass_inj_table.xml, l.5): Could not find solver  named 'comp'.
No flow solver has been found.

[MelReyCG]

To target the solver attribute (xml line):

Suggested change

	getDataContext(), solverName );
	getWrapperDataContext( SolverType::coupledSolverAttributePrefix() ),
	solverName );

then you can remove the string const & solverType parameter from throwSolversNotFound()

[MelReyCG]

try to remove useless

[MelReyCG]

2 useless linebreaks