feat: Additonnal context writeStatistics for misappropriate values

[arng40]

Add GEOS_WARNING for the writeStatistics attribute in case of misappropriate values.

Example with hydrafratureSinglePhase2d.xml

 <Hydrofracture
      name="hydrofracture"
      writeStatistics="all"
      solidSolverName="lagsolve"
      flowSolverName="SinglePhaseFlow"
      [...]
    </Hydrofracture>

    <SolidMechanicsLagrangianFEM
      name="lagsolve"
      writeStatistics="iteration"
      [...]/>

    <SinglePhaseFVM
      name="SinglePhaseFlow"
      writeStatistics="iteration"
       [...]/>

We cannt output iteretion information for both lagsolve & SinglePhaseFlow, here the following warning

***** WARNING
***** LOCATION: /path/to/src/coreComponents/physicsSolvers/PhysicsSolverBase.cpp:152
***** Controlling expression (should be false): canOutputIteration
The lagsolve solver cannot output convergence statistics
You can set writeStatistics to `convergence` 

***** WARNING
***** LOCATION: /path/to/src/coreComponents/physicsSolvers/PhysicsSolverBase.cpp:152
***** Controlling expression (should be false): canOutputIteration
The SinglePhaseFlow solver cannot output convergence statistics
You can set writeStatistics to `convergence`

[MelReyCG]

About the behaviour, when all is requested but only iteration or convergence are allowed, we should have a warning.

[MelReyCG]

I suggest to implement the comparison between what can be output and the user request in the cleanup(), because other components can interact with the iteration / convergence output.
Compare *Stats::m_csvOutputOpened and the user input.

[Copilot]

Pull Request Overview

Adds warning messages to inform users when statistics output configuration is inappropriate for the solver type. The PR implements validation logic that checks if solvers can properly output the requested statistics type and provides helpful suggestions to users about the correct configuration.

• Adds GEOS_WARNING messages for mismatched statistics output configurations
• Refactors statistics classes to use clearer naming for output request vs. opened state tracking
• Changes default density model type from linear to exponential in schema

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/coreComponents/schema/schema.xsd	Updates default density model type from linear to exponential
src/coreComponents/physicsSolvers/SolverStatistics.hpp	Refactors member variables and methods for clearer naming and adds documentation
src/coreComponents/physicsSolvers/SolverStatistics.cpp	Updates implementation to use renamed variables and methods
src/coreComponents/physicsSolvers/PhysicsSolverBase.hpp	Updates comment documentation for statistics parameter
src/coreComponents/physicsSolvers/PhysicsSolverBase.cpp	Adds warning logic for inappropriate statistics configurations and improves documentation

Comments suppressed due to low confidence (1)

src/coreComponents/physicsSolvers/SolverStatistics.cpp:1

• Using insert() instead of assignment operator will not update existing keys. This changes behavior from the original code which used assignment. Use m_residuals[key] = value to maintain the same behavior.

/*

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Corrected spelling of 'ib' to 'in'.

Suggested change

	* @brief Set a residual value given a key ( column ib the CSV )
	* @brief Set a residual value given a key ( column in the CSV )

[Copilot]

Missing space before assignment operator. Should be 'wrongConvergenceCSVOutputRequest = ' for consistency with coding style.

Suggested change

	bool wrongConvergenceCSVOutputRequest= getConvergenceStats().getCSVOutputRequest() &&
	bool wrongConvergenceCSVOutputRequest = getConvergenceStats().getCSVOutputRequest() &&