Feature 1824 pb2nc log message for mlcape

[hsoh-u]

Expected Differences

The log message: The number of derived CAPE includes the MLCAPE. They are separated

DEBUG 3: Derived CAPE = 368 Zero = 146
DEBUG 3:        not derived: No cape inputs = 189       No vertical levels = 19664
DEBUG 3:        filtered: 0, 0

==>

DEBUG 3: Derived CAPE = 184     Zero = 62
DEBUG 3:        not derived: No cape inputs = 189       No vertical levels = 19664
DEBUG 3:        filtered: 0, 0
DEBUG 3:
DEBUG 3: Derived MLCAPE = 184   Zero = 84
DEBUG 3:        not derived: No cape inputs = 189       No vertical levels = 19664
DEBUG 3:        filtered: 0, 0

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

/d1/personal/hsoh/git/features/feature_1824_pb2nc_MLCAPE3/MET/met/bin/pb2nc /d1/personal/hsoh/data/CAPE_data/prepda.2018091100 ./prepda.2018091100.add_cape.nc /d1/personal/hsoh/data/config/PB2NCConfig_cal_cape -v 3 -nmsg 10%

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]

• Do these changes include sufficient testing updates? [No]

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select Linked issues with the original issue number.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[JohnHalleyGotway]

I approve of this PR. I confirmed that the GHA testing workflow flagged no differences. I reviewed the code changes and see the requested change to the log message in pb2nc.cc but do also see changes to 3 other files. I assume those changes are to satisfy issues raised by SonarQube scans.

Thanks for enhancing the logging.