I agree in general the tools are lacking but if you use AWS,GCP, or w/e you get a huge boost on the tooling.
I see the point of microservices for cases where you want to use different tech stack for one part of system or need special scalability. I don't see the point in going that route to only have separation between components or being able to split work.
If you are afraid that you won't get the monolith architecture right, you should be afraid of the same thing with microservices.
I hate this phraseology, and IMO it's a telltale sign of a new or inexperienced professional developer (another variation: "replace jet engine while in flight"). All non-greenfield development forbids breaking the existing system in order to make changes. This is a daunting responsibility, but it's inherent and assumed, so only college kids who have never had to maintain a running system before talk about it like it's noteworthy.
If someone needs a microservice architecture to support team growth, it just means they don't know how to manage a team, and have to let every dev or pair of devs have their own little kingdom.