Create MAPL.profiler logger

[mathomp4]

Description

This PR creates a new MAPL.profiler logger and moves some current writes to use logger:

• Model throughput
• Per-component timers
• Global timers

For GEOS, this will create pretty much the same log output as long as:

   MAPL.profiler:
       handlers: [console_plain]
       propagate: FALSE
       level: WARNING
       root_level: INFO

is in logging.yaml. As such, an PR will be needed for GEOSgcm_App (see GEOS-ESM/GEOSgcm_App#391)

Related Issue

Closes #1930

Motivation and Context

This will allow users to have most of MAPL at WARNING LEVEL but have the timers always output.

How Has This Been Tested?

Tested with GEOS. Zero-diff.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Trivial change (affects only documentation or cleanup)

Checklist:

• I have tested this change with a run of GEOSgcm (if non-trivial)
• I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
• I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

[mathomp4]

@tclune Please take a look at this. It was a pretty one-for-one swap of writes to logger. But perhaps I'm now violating how logger should be used with things like logger-on-one-process:

      if (my_rank == 0) then
         report_lines = reporter%generate_report(t_p)
         lgr => logging%get_logger('MAPL.profiler')
         call lgr%info('Report on process: %i0', my_rank)
         do i = 1, size(report_lines)
            call lgr%info('%a', report_lines(i))
         end do
      end if

[tclune]

Ooh nice. I had no idea that this was being worked on!

[lizziel]

Looks good to me! Thanks for putting this together.