It's not a tooling problem. It's more of a layer of policy problems. If you realize that you cannot run a simple experimental code even in non-production environment for weeks due to 10s of privacy, security, access, process and legal issues where you gotta collect a bunch of approvals, this is critical. And the problem gets worse because the tooling is too good when it enforces. There used to be some holes and circumvention which are all gone these days. This is probably why they said "the infra is good for services but not for research".
I don't even think it's good for services. It's not like you go through cumbersome reviews/tools and then things are safe. They have insane homemade config languages and obscure systems that 99% of SWEs don't really understand but won't say it out loud. That's how they dropped cns2, and the postmortem is never going to blame the tools.