GCK and GDK should be able to co-exist

I find myself in a situation where my GDK setup frequently breaks, and GCK makes certain workflows more difficult (such as performance analysis) so I would like to run them side-by-side. This currently seems to not work well, because:

1. You either need to check out all gitlab repos twice (once for each GDK, GCK) and maintain all work and branches twice. This makes switching back and forth between GDK/GCK impossible in mid-work, since your local changes do not carry over. You could push WIP commits I suppose but if it's just e.g. profiling code you added, that's not typically something you want or should push remotely. Also some things like stashes do not carry over at all.
2. You create symlinks to a single checkout. This is what I currently do. However, because the GCK assumes a different directory structure for the location of many configuration files that the app itself reads (such as /home/git/shell-secret which only exists in a container), it will break when run under the other "kit".

Therefore I currently find that GDK and GCK are mutually exclusive choices, which is unfortunate. It would be good to pinpoint what causes friction between the two and decouple them, so one doesn't have to opt for 1. The gitlab.yml is one such point of friction, since it's written by either kit. So is puma.rb where I had to manually tweak config to make it work with the GCK after coming from a GDK installation.