Flows: Improve the Log Activity Panel

Flows is totally cool! But the log panel has (in my opinion) UI/UX issues. I find myself immediately reaching for Postman to debug/setup just about any flow. In this discussion, I'm going to address what I consider to be the biggest pain points with the Log panel. Then at the end, suggest an alternative *(wireframe/rough-draft)* UI layout to try to address these pain points. --- The activity Log menus are not a 1:1 mapping to the flow object When you toggle open $trigger, it has $accountability nested in to it. <img width="308" alt="Screen Shot 2022-10-03 at 11 52 36 AM" src=" In reality, $accountability is actually a sibling key on the Flow Object. *(note: Since options is nested in the Data Studio log panel, at a glance it seems like it exists on the flow object, though it doesn't.)* ![CleanShot 2022-10-03 at 11 52 54]( On a similar note, $last is not provided within the logger at all. I'd guess the justificati…