Evidently some disagree, but I'm on your side. Biggest reason I didn't immediately think of "But what would I use for a keyboard" is my Q25 has on built-in.

UnifiedPush, F-Droid, a GMaps webview (arguably cheating, but I'm not RMS), NewPipe or Invidious are all good-enough alternatives, but I remember struggling to find a keyboard that felt right when I was using a Pixel 2 for a fortnight.

I think I went with the oldest Fleksy or Minuum APK I could find (from a reputable source), as they were fine without GApps.

Though I'd also like to call out the fact that AOSP has talkback, the accessibility service built-in, but there's no AOSP TTS engine to use it with. This is especially noticable when trying to use any spoken directions in OSMAnd, as it requires a TTS engine to use that function.

The only reason it's not the dumbest thing about Google's stewardship of AOSP is that I'm not sight impaired - as it stands, the multi-trillion-dollar corporation ripping out the built-in SIP client in their phone OS takes that prize