Improve Logging on State Transitions

[jwang-copilot]

As someone trying to debug why a transition is not occurring, I'd like to see additional logging of what that state was that it was trying to transition from -> to in addition to the logs including which SM ID and event IDs are involved. For example, unexpected event transition from open to re-open [....

[z-cran]

@jwang-copilot @YulyTenorio @massenz
Looking to resolve this request through #46

An example changes from this PR and from other recent commits:

2022/10/04 17:47:21 listener.go:59: Listener[DEBUG] Received request event_id:"39e176cd-4856-418f-a287-fee93d33029e" timestamp:{seconds:1664905641 nanos:744012453} transition:{event:"fail"} originator:"statemachine-lambda-client"
2022/10/04 17:47:21 listener.go:107: Listener[INFO] Event `fail` transitioned FSM [b9cad624-bf5a-43c5-8fb8-27bb64de18e8] to state `failed` from state `ingested` - updating store

Fields tracked:

• State transitioned from (info)
• SM ID (info)
• Event ID (debug)