I think there's a lot more than you might initially realize. A few of the top of my head (beyond your ORM): automapper, 3rd-part json or Polly, logging, server-side validation, many more. Another vector: unlikely a lot of other languages I've found way more .net libraries for 3rd party connectors or systems are community-based.
.NET definitely includes more these days, including lots of the things I've mentioned above, but they're often not as good and you likely have legacy dependencies.
I disagree. I also believe you might be equating your preferences with necessities. Much of what you listed is absolutely not needed, and often just brings in more external dependencies of questionable benefit. Take AutoMapper, for example, I cannot stand the tool, but many people enjoy it. I (sarcastically) bet many were thrilled when Jimmy, the maintainer decided to change to a paid license years after its release and heavy adoption.
I would argue .NET is roughly just as feature packed as many other frameworks, if not more so. I am glad many popular 3rd-party libraries are not baked into .NET. I do not want frameworks to be rife with garbage no one needs. Keep them lean and keep them mean.
Though, I will agree with you on logging. I do believe that the 3rd-party solutions are better.