Track batch execution time for microbatch models

[QMalcolm]

Resolves #10825

Problem

We weren't tracking the execution time of batches for microbatch models. Thus, we were always logging that they took no time to run (0.00 seconds) which didn't actually match reality.

Solution

Begin tracking the time it takes for a batch to run, and propagate that information to the batch run result.

Checklist

• I have read the contributing guide and understand what's expected of me.
• I have run this code in development, and it appears to resolve the stated issue.
• This PR includes tests, or tests are not required or relevant for this PR.
• This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
• This PR includes type annotations for new and modified functions.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.17%. Comparing base (6b9c1da) to head (1e2e23a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10828      +/-   ##
==========================================
- Coverage   89.19%   89.17%   -0.02%     
==========================================
  Files         183      183              
  Lines       23402    23404       +2     
==========================================
- Hits        20873    20871       -2     
- Misses       2529     2533       +4     

Flag	Coverage Δ
integration	86.47% <100.00%> (-0.03%)	⬇️
unit	62.11% <50.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Unit Tests	62.11% <50.00%> (-0.01%)	⬇️
Integration Tests	86.47% <100.00%> (-0.03%)	⬇️