This has been my org's issue as well. We use dedicated, external products for project management, CI, binary asset storage, container registry, wiki, etc etc. I get that a one-stop shop might be really valuable for a small org with basic needs that align well to what GitLab supplies, but I don't know if it scales up all that well. I would worry about getting partly migrated and then discovering some functionality gap, and maybe finding out that the GitLab team that built that feature no longer exists and there was basically no one maintaining it any more.
Spreading themselves so thin does have a real cost— here's an example of recently-resolved ticket for something that I would consider core "repository" functionality (LFS content inclusion in the tarball) but that sat unfixed and unnoted-in-docs for almost four years: https://gitlab.com/gitlab-org/gitlab/-/issues/15079
We did evaluate silver (now premium), and it wasn't worth it. We will probably upgrade, but this is a 5x increase on the price, and as a long term contributor of Gitlab, this does definitely make me angry.
>issue dependencies
FWIW these are available in Gitea, along with some other Gitlab features that require payment.
It's a much more lightweight alternative, though.