Implement functions and classes in ngen to produce Catchment output netcdfs [NGWPC-10597]

[sivasankkar]

Enable functionality in ngen to write all catchment outputs to a netcdf file for non-MPI ngen runs. This PR is created following NGWPC-9011 PR (#106). However, that didn't make it into development because it remained in draft. We squashed all earlier commits and rebased with ngen development for this PR. This functionality does not work on MPI runs.

Additions

• NetCDFCreator.hpp - header file for creating a class that can handle all netcdf operations.
• NetCDFCreator.cpp - class file for methods/functions to handle all netcdf operations.
• NetCDFCreatorTest.cpp - class containing two unit tests - one for the catchment and another for the output values.

Removals

Changes

• NetCDFCreator.hpp and cpp: Functions to create and write catchment output variables to netcdf file.
• Bmi_Formulation.hpp: Added get_output_variable_units and set_output_variable_units function to obtain the output variable units to write to netcdf attributes.
• Bmi_Module_Formulation.cpp and Bmi_Multi_Formulation.cpp: Set the output variable units read from realization config.
• NgenSimulation.hpp: Included netcdfcreator header and pointer for that class.
• NgenSimulation.cpp: Added a function call to write the output variable values to netcdf after every time step.
• Formulation_Manager.hpp: Added a function to retrieve all catchment formulations for iterating through for netcdf creation.
• Layer.hpp and cpp: Added a function to gather catchment outputs to a vector for each timestep.
• NGen.cpp: Added a message for MPI runs and a function call to create the NetCDF writer/creator instance for non-MPI runs.
• CMakeFiles for ngen and test - Created a library for the NetCDFCreator and set up target link libraries appropriately.

Testing

1. Tested with CNF data with 67 catchments. The NetCDF output file was created successfully for non-MPI runs.
2. Appropriate log message was added for MPI runs.
3. Appropriate log message was added when no output variables were mentioned in the realization config.
4. Unit tests

Screenshots

Notes

Todos

Checklist

• PR has an informative and human-readable title
• Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code follows project standards (link if applicable)
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future todos are captured in comments
• Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• Reviewers requested with the Reviewers tool ➡️

Testing checklist (automated report can be put here)

Target Environment support

• Linux