To be honest, I understand the potentially good intentions behind Google's push to manage keys for app developers. It is not trivial to (1) keep private keys secure, and (2) not lose access to them over a long enough period of time. So Google can store them in HSMs in their datacenters and provide backups and access controls and such. But it also gives them the ability to deliver app updates with "extra stuff" for targeted individuals. See Figure 1 of [1]. That doesn't look very nice to me.
[1] https://developer.android.com/studio/publish/app-signing
I wonder if there's an internal fight between the Tools and Play teams, because all of this should be possible via the Gradle plugin, but understandably the Play team probably wouldn't see high adoption of APK splits if it required configuration via the morass of crap that is Gradle.
It is pretty typical of Google to choose the most invasive solution.