ref(workflow_engine): Update workflow evaluation log data

[saponifi3d]

Description

This PR is accomplishing two goals:

1. Makes sure we have all the data required to evaluate the tagged_event condition, this uses the workflow engine logger / context, and will log for opt'd in orgs only.
2. Update the generic logging to include as much info as possible in the log. This meant changing models to snapshots, and lists of models to id lists, and adding a few more data items (the conditions being evaluated).

Hoping that after this, we can at least root cause any issues with the specific problematic condition handler and that we'll have enough evaluation info at the top level, that it will include all the required information for us to determine why an alert did / did not trigger. (eventually, it'd be nice if this could live in something like BigTable or Cassandra so we can query the info, reduce logging costs, and let users see the alert evaluation information if they want)

[saponifi3d]

this is just incase the top level logs don't show me everything, i want to be able to handle the user case(s) around this specific handler.

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[kcons]

• The snapshotting is cool; I think it might be nice to have a ABC with to_snapshot() -> dict[str, Any] just as a way to make the convention explicit: this is a method to produce a loggable, storable, jsonable representation of the current configuration to aid in debugging, not some other notion of snapshots.

[saponifi3d]

@kcons 👍 love the idea. since i have typed dicts for all the snapshot stuff, i used a generic instead of dict[str, Any] to have a bit more type safety as well. lemme know what you think!

---

😭 -- reverted this change because of the collision with ABC + BaseModel. Can reinvestigate later, i think we'll have enough type safety through the classes now and we can push for consistency 🔜