I started to add a button to filter by "materializations" but it felt weird that it cleared the search. Instead, I made the log filtering bar use the same tokenized text field / typeahead that the runs and solids pages use. The autocompletions show you that you can filter by type or step which should make those features more obvious. Also nice to consistently use the same UI for faceted search.
Run snapshot tests
Will revisit this one Friday - I think that this will require a few changes to the tokenizing input to allow the intermediate state to be observed but we can probably do it in a clean way.
Small note about this one—I made it search / filter as you type but didn't implement debouncing within the tokenizing text field. The old vesion of this control didn't debounce (so the performance shouldn't be any worse than before) and I think that we should actually try to move the log filtering to a web worker or idle callback so that the filtering itself is async. Debouncing the input will likely just make the jank happen at a different moment 😅