Create LogNodeResult event

[aranke]

Problem

We need a new event to log generic node result events with dynamic messages.

Solution

Create a new LogNodeResult event

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 88.87%. Comparing base (7106005) to head (3c4e191).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11195      +/-   ##
==========================================
- Coverage   88.93%   88.87%   -0.06%     
==========================================
  Files         187      187              
  Lines       24057    24099      +42     
==========================================
+ Hits        21395    21419      +24     
- Misses       2662     2680      +18     

Flag	Coverage Δ
integration	86.18% <60.00%> (-0.13%)	⬇️
unit	62.41% <100.00%> (+0.35%)	⬆️

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

Components	Coverage Δ
Unit Tests	62.41% <100.00%> (+0.35%)	⬆️
Integration Tests	86.18% <60.00%> (-0.13%)	⬇️

[gshank]

It seems odd that we'd load up the event with a dictionary of status_to_message_map, when at the time we do that, we'd in theory already have the status. Is there some reason to do it this way instead of simply loading the appropriate message?

[aranke]

@gshank Good catch, looks like I can simplify further which I have done.
Could you please re-review this PR? Thanks!