Yeah, they'll include a dongle that will break in less than a year with very casual use. Ask me how I know.
Also, I already have headphones. I don't want Google's USB C headphones. They wouldn't need to include any of this junk with the phone if they didn't remove the jack in the first place.
This is not the model I have, but I've something very similar by Anker https://www.amazon.com/Roav-Bluetooth-Noise-Cancellation-Int...
EDIT: Sidenote, I don't know how much I'd trust cheap bluetooth adapters re: security... there is a non-zero chance it's spewing my conversations out, ripe for anyone w/ the proper equipment to listen in. <Tin Hat />
Supply chain issues notwithstanding, I think you're pretty safe with a CSR bluetooth chip - they're in everything. Whether it's a clone or an original though, no idea.
You can say that's not Google's fault, and that it doesn't apply to Pixel devices specifically. But like it or not, Google chose to vomit their platform across dozens of manufacturers and thousands of devices. If they didn't want the kind of chaotic inconsistency exampled above, they should have gone with the iPhone/Pixel approach from the beginning.
And there are _very_ few third-party options that work with the Pixel lineup -- not necessarily Google's fault, but early adopters of the no-3.5mm trend are being punished while the market catches up.
Also, I already have headphones. I don't want Google's USB C headphones. They wouldn't need to include any of this junk with the phone if they didn't remove the jack in the first place.