I think it's not really about the tech but the constraints and the goals of your project with the resources you have.
For a lot of CRUD use cases a Web App/SPA is not really needed and a classic "monolith" can go quite far, and for this I find Rails still unmatched (maybe Django or Laravel too but I'm not familiar with it). You can have something up and running with nearly everything you listed in a week-end.
If you need a SPA you can still use Rails in API mode in the back-end with a front in React/Vue.
And if you are not about short-term productivity gains and looking for more long-term maintainability and scalability, then you can have multiple services in any language that fits you (static typing, ...) using the appropriate micro-framework for each.
For a lot of CRUD use cases a Web App/SPA is not really needed and a classic "monolith" can go quite far, and for this I find Rails still unmatched (maybe Django or Laravel too but I'm not familiar with it). You can have something up and running with nearly everything you listed in a week-end.
If you need a SPA you can still use Rails in API mode in the back-end with a front in React/Vue.
And if you are not about short-term productivity gains and looking for more long-term maintainability and scalability, then you can have multiple services in any language that fits you (static typing, ...) using the appropriate micro-framework for each.