Thanks for both of your replies!
The reason I wanted to do this is that I had a flow that might be called something like "run dbt" or "run dbt tests" that called another util task I created called run_dbt that sets up all the connection parameters, injects variable in the statement to run and so on before finally calling trigger_dbt_cli_command with the constructed statement. I didn't see a purpose in "run dbt" showing up as its own flow.
I created a workaround I'm happy with anyway, I converted run dbt to a function that returned a finished config dictionary instead, that I can easily pass to the trigger_dbt_cli_command task directly from the flow. Just a minor change in how things are set up. I don't mind changing things around for Prefect 2, the new solution isn't worse or better. I just wanted to make sure I wasn't missing something obvious and now I know. 🎉