[UI v2] feat: adds query to join flow runs with parent flow

[devinvillarosa]

[UI v2] feat: adds query to join flow runs with parent flow

This query is needed for a basic flow runs table (until the APIs get updated to include both flow_id and flow_name)

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

Relates to #15512

[pleek91]

would we be better off creating a single query action that does this? That way we can await the flow runs, await the flows, and then combine them. And then we can just use a normal query rather than this custom hook with its custom pending an error states.

[devinvillarosa]

I remember seeing a thread with @desertaxle where we would want to do it this way, so that we won't find ourselves writing so many specific queries for joining data.

Should we continue doing this way?
I do see the benefit of having nice RQ object, but it can become an anti pattern to write specific joining queries vs using re-usable query configs.

@devangrose @desertaxle Any thoughts on how we should continue joining data?