feat!: session lifecycle log improvements

[jusiskin]

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

The worker agent logs for session lifecycle events was ad-hoc and inconsistent

The previous PR (#49) was intended to include changes that were missed. That PR description has since been edited to reflect the actual changes made.

What was the solution? (How)

Made the logging message formatting structure consistent. The format for session events is:

[<SESSION_ID>] [<SESSIONACTION_ID>] (<SESSIONACTION_HUMAN_READABLE>): <MSG>

Where:

• <SESSION_ID> — The unique identifier for the session
• <SESSIONACTION_ID> — The unique identifier for the session action
• <SESSIONACTION_HUMAN_READABLE> — A more human-friendly representation of the session action that denotes the job model entity that the action definition belongs to
• <MSG> — The event message

An example of the new session log is:

2023-10-06 05:13:47,039 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71]: Session started
2023-10-06 05:13:47,142 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71] [sessionaction-6a7080641d5440c78a5f379b287c2b71-0] (environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].enter()): Starting action
2023-10-06 05:13:47,150 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71] [sessionaction-6a7080641d5440c78a5f379b287c2b71-0] (environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].enter()): Action completed as SUCCEEDED
2023-10-06 05:13:47,251 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71] [sessionaction-6a7080641d5440c78a5f379b287c2b71-1] (step[step-e404e034a52846809db3ec250ea82f48].run()): Starting action
2023-10-06 05:14:32,379 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71] [sessionaction-6a7080641d5440c78a5f379b287c2b71-1] (step[step-e404e034a52846809db3ec250ea82f48].run()): Action completed as SUCCEEDED
2023-10-06 05:14:32,852 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71] [sessionaction-6a7080641d5440c78a5f379b287c2b71-2] (environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].exit()): Starting action
2023-10-06 05:14:32,861 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71] [sessionaction-6a7080641d5440c78a5f379b287c2b71-2] (environment[STEP:step-e404e034a52846809db3ec250ea82f48:myenv].exit()): Action completed as SUCCEEDED
2023-10-06 05:14:33,043 INFO [deadline_worker_agent.sessions.session] [session-6a7080641d5440c78a5f379b287c2b71]: Session complete

What is the impact of this change?

• Logging is more structured and internally consistent and easy to filter with basic text searches
• Since identifiers are fixed length, the log messages for session lifecycle events align vertically unless word-wrapping

How was this change tested?

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

Was this change documented?

No

Is this a breaking change?

Yes, log formatting has changed