Make OnlineLogging more flexible

Currently, the `OnlineLogging` submodule is somewhat inflexible, making it difficult to adopt in other CliMA packages. For example, [`_update!`](https://github.com/CliMA/ClimaUtilities.jl/blob/2a94de9819d18d1dbd94ecaf871a69976603bf50/src/OnlineLogging.jl#L58-L104) requires an `integrator` object that not every model has, and [`report_walltime`](https://github.com/CliMA/ClimaUtilities.jl/blob/2a94de9819d18d1dbd94ecaf871a69976603bf50/src/OnlineLogging.jl#L182-L218) is extremely specific with no options to customize the output. For these reasons, we opted to [design our own custom logger](https://github.com/CliMA/ClimaCoupler.jl/pull/2026) in ClimaCoupler.

Ideally, we could rewrite this submodule to be slightly more abstract. Alternatively, we could scrap it and just accept that each model will have its own custom logging code.

Read src/OnlineLogging.jl, especially _update! and report_walltime, then compare their assumptions with the custom logger in the linked ClimaCoupler pull request. Determine whether a reusable abstraction is feasible or whether this submodule should be removed; the issue does not define a concrete implementation or acceptance criteria.

Written by the indexing model from the issue text.