Google employees could resolve this. They've dissented for various reasons before, and changed internal policy, why not with this?
It's hard to support a heterogeneous space of user agents running on a heterogeneous set of platforms. Eventually, abstractions break and you end up with a weird bug that only manifests on such-and-such browser in so-and-so configuration.
How much easier life is if you only have to support a few browsers on hardware that checksums to have a known-good configuration...
Chasing down render errors in the deep interactions between declarative HTML rendering and an esoteric-but-important hardware / software configuration is drudgework.
Some of my best ideas even, came out of clearing drudge.
Google employees are the ones writing this code, doing the designs, the QA, the project planning.
You can't expect the people who work for these companies to do the right thing. Time and time again, it requires outside forces. Either customers or legislation.
Gen Z knows nothing of what the web was once like, and lots of folks now embrace companies being stewards of the commons, eg. Apple App Store.
There's also the current down hiring market and macro economic conditions.
In hindsight, perhaps none of us should have been surprised the latter was a better proposal for most people.