feat: log session action completion events

[jusiskin]

What was the problem/requirement? (What/Why)

Session action completion events were not being logged

What was the solution? (How)

Added logic for logging session action completion events.

What is the impact of this change?

All session and session action lifecycle events are now emitted

How was this change tested?

• Automated unit tests were added
• Manual end-to-end testing

Was this change documented?

No

Is this a breaking change?

No

[ddneilson]

Solid improvement, Josh. However, this -- environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].enter() -- sort of message in the log has been identified as being the opposite of human readable; there's a ticket that calls it out explicitly. It's readable to programmer-minded individuals, but little else.

Do you have thoughts on how that can also be improved?

One idea: environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].enter() -> "[<stepid>] Entering Environment: myenv". Ideal might have been "Entering Step/Job/External Environment...", but the Worker doesn't have that context.

[ddneilson]

Solid improvement, Josh. However, this -- environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].enter() -- sort of message in the log has been identified as being the opposite of human readable; there's a ticket that calls it out explicitly. It's readable to programmer-minded individuals, but little else.

Do you have thoughts on how that can also be improved?

One idea: environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].enter() -> "[<stepid>] Entering Environment: myenv". Ideal might have been "Entering Step/Job/External Environment...", but the Worker doesn't have that context.

Let's take this improvement as a followup.