That's funny because I read this entirely differently (somewhat dependent on context)
"A decision was made to..." is often code for "The current author didn't agree with [the decision that was made] but it was outside their ability to influence"
Often because they were overruled by a superior, or outvoted by peers.
That's funny, I always thought that meant, "my superior told me I had to do this obviously stupid thing but I'm not going to say my superior was the one who decided this obviously stupid thing." Only occasionally, that is said in a tongue-and-cheek way to refer directly to the speaker as the "superior in charge of the decision."
That reads like several comments I've left in code when I've been told to do something very obviously dumb, but did not want to get tagged with the "why was it done this way?" by the next person reading the code
Usually the passive voice is used at work to emphasize that it was a team/consensus decision, adjacent to the blameless incident management culture. It’s not important that one engineer or PM pushed it, but that ultimately the decision was aligned on and people should be aware.
Although arguably it would be clearer with the active voice and which specific teams / level of leadership aligned on it, usually in the active voice people just use the royal “we” instead for this purpose which doesn’t add any clarity.
Alternatively sometimes I don’t know exactly who made the decision, I just learned it from an old commit summary. So in that case too it’s just important that some people at some time made the decision, hopefully got the right approvals, and here we are.
It means "I decided to do this, but I don't have the balls to admit it."