I have been on both sides of this coin.
I was working on an automation team and team where the SW platform architect was trying to make us change our primary scripting language and infrastructure, to the point where he tried strong-arming our manager into making those decisions.
But then I’ve also been told to do it all myself, even when there was no time, or budget, or buy-in from any of the teams.
In reality, it needs to be a collaborative effort, we all can bring different things to the table to bring an automation narrative to the fore.
For me, it’s important to decide what your automation requirements are (including what you want to automate and why) in as agnostic a way as you can, before making decisions about tooling and language. It shouldn’t be a solely test team or dev team (if those are separate teams) but one that we all own, sure there might be some who work on it more than others, but its purpose is to benefit everyone, so we should all be invested in it.
It can be the case that there needs to be a point of contact of decision maker, or champion or whatever.