#3481 [Core] Better execution search capabilities (search by inputs) Issue created by michaels-lyft Motivation: Why do you think this is important? This would allow us to quickly find a past execution based on either inputs, outputs, sub-task/workflow names, launch plans, or logs. In the past, we've run into situations were we would like to restart a workflow from a few days/weeks ago. But we had to resort to a linear search in order to find the right one. Goal: What should the final outcome look like, ideally? A search bar somewhere on the UI that either allows for more complex search languages (like Kibana or Sourcegraph) or have more attributes that can be used to search (eg. one attribute each for input, output, sub-task name, sub-workflow name, logs). Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte