Ignoring what "legally" forced entails, and just focusing on the mechanics of renaming stuff: Even if your code base can be updated with a simple "s/old/new/" regex (and, IME, this never, ever works as well as you thought it would, and always creates a long tail of manual grepping and editing), you still have to fix the docs, deal with breaking API changes, support multiple versions, provide upgrade paths, deal with confused users, etc. etc. etc.
And, um, confusingly, the examples you cite are actually even more complicated and work-intensive than what is being talked about in this article, because they also require URL / domain name updates, legal document changes, regulatory filings, etc. etc.
TLDR: the contention that "name changes happen easily" is not an accurate description of the situations you are citing.
Otherwise it would have been smoother
Considering how much effort we had to out into fixing pipelines because of hardcoded scripts, and the lack of good reason to do it its no surprise that it was scoffed at. White keyboard warriors needed to make a change, but couldn't do anything meaningful as it would require actually doing something.
At least this change makes sense.
It certainly helped GNOME whom was one of the biggest proponents /s
I'm generally in favor of DEI, btw, so you can lose me with your bigotry.