Verbosity for debugging

Hi there 👋🏼

In CI this action is taking a _long time_ which i suppose is because it runs all of the migrations. In this run, for example, it takes 6 minutes, more than what my tests and build take to run.


(I've previously raised the issue of [being able to skip hooks](https://github.com/geldata/gel-cli/issues/1602), which later should be an option here i guess, but they're already commented out here, so no worries there.)

I would love at least some way of adding verbosity to understand what is taking this much time. Is there a way for doing that?

Thanks!

Start by locating the action entry point responsible for running setup and migrations, then reproduce the slow CI run to identify where timing or command output is currently hidden. Done means providing a usable verbosity option that reveals the work taking time and documenting how to enable it.

Written by the indexing model from the issue text.