Maybe we shouldn't be, but it's still a problem that regularly needs to be solved.
In any case, I need to refute your argument, in my work as software engineer spanning more than a decade, I have noticed zero deprecation of my skills (Java, SQL, HTML/JS/CSS) (while keeping them up to date!) until now and only had to learn a few new complementing skills (cloud, docker, SPA, Kubernetes). The only skill that got replaced might have been "Java application server management" since that got replaced by whatever docker runtime is en vogue at the moment. I have worked for the government and met PL1/Cobol mainframe programmers that refused to learn Java and still got paid generously for their long term expertise.
I can see how you might think that... until you start actually talking in depth with enough actual users and executives and trying to get them to agree on how all that stuff should work and what it should be capable of.
Most of the development process is about trying to wrangle abstract ideas about how business logic should be implemented/improved from flawed humans who aren't great at communicating those ideas. Your 'simple' CRUD app still often has to be highly customized by someone willing to do the difficult work of dealing with people. And that's before you even start getting into working with more regulated businesses.
Code monkeys/plumbers using 'outdated' tech who can deliver something that makes a workplace more efficient in the long run will continue to be in demand. There was enough functionality in software by the 1970s to handle the vast majority of business needs. Someone still has to understand those businesses needs (which ultimately have little to nothing to do with software) well enough to translate them into something that works. Whether it works for those who are using it is all that really matters.
I’ve worked with tons of programmers like you describe. I’ve continued to tell them that simple UIs and CRUd interfaces to dbs are solved problems we should not be fighting with.