"Main reason and the only microservices advantage - ability to split teams."

This is simply not true. What about rolling updates? Independent scale in or out? Reliability, meaning that if something fails you just need to restart one component only. What about developing each component using different languages and stacks.

And the term "microservice architecture" exists, and is a valid term. There are several architectural choices you should make, like what are your message passing techniques and why?

So, yes, a microservice architecture is more complex. It might have higher initial operating expenses, but then you could scale in individual components that are not used that much and save money on resources. And yes, you should have a very well established CI/CD pipeline, but this is actually a good thing. Would you build, test, package and deploy your code manually?