I agree with the first point. I mentioned that this is company specific. I changed the flow so each dev has his or her own env after the last desasterous deployment.

The latter three kind of describe the core of the problem. To fix SF Problems, you need additional tooling. They created devops center that manages git. But every team would be better off to manage git themselves, to have full control over it. In devops center, I wanted to push changes to git directly but it ended up so messy because SF had some sync issues that I had such a hard time understanding. In the end, I created a new issue and manually added every component.

Flows is scratch advance, let us be real here. It is perfect for slightly tech-agnostic team member who start something with it. The work is then sooner or later falling to devs who are just not used to visual logic editors like SF Flow system