Allow entering the container to debug its state

[aleixpol]

Is your feature request related to a problem? Please describe.
I am trying to debug a crash in a process using this tool. I'd need to run again one of the processes with gdb and interact with it.

Describe the solution you'd like
I'd like to be offered a way to interact with the system as one of the tests fails.

Describe alternatives you've considered
I looked into modifying our ci tooling to call the processes by default with gdb, can't really do that without breaking our current ci as we get the recipes from elsewhere shared.

Additional context
This is the CI in question:
https://invent.kde.org/plasma/kwin/-/blob/Plasma/5.27/.gitlab-ci.yml?ref_type=heads

[firecow]

You need to make a more precise description of what you want here.

How would you like the command that puts gitlab-ci-local in "debugging-mode" to look like?

[aleixpol]

I can imagine running gitlab-ci-local $job --shell bash or even just gitlab-ci-local $job --devel and after it executes the CI suite you're given a shell with the environment where the system just ran. It would be a good opportunity for running the CI, modifying the code and running again or just generally learning about the execution.