This is, in my mind, a classic example of where functionality exists within Woocommerce that should be up streamed into Wordpress. I really wish that Woocommerce devs would treat Wordpress as a framework their own software as a specific permutation. This would mean contributing back upstream any additional functionalities they need, and then building out their specific implementation on those new functionalities. Instead, there's been a consistent pattern of building out Woocommerce itself as a framework, leading to more and more fragmentation and functionality silos in the Wordpress ecosystem.

It may seem unfair to pin this to a single project, but the significance of Woocommerce is nothing to be sneezed at, both by the size of it's adoption, it's virtually singular status for what it represents, and the fact that both projects are run by teams under the same corporate umbrella.

Other functionalities that exist or are being developed within Woocommerce but not Wordpress include the ability for an end user to manage custom taxonomies (Product Attributes), content reviews management, commercial-plugin licensing management, and the ongoing work on performance-oriented dedicated-entity data tables.

On another note, and in addition to the above, I, for one, would be in favor of enabling the block editor for taxonomies, allowing for a much richer suit of possibilities for building out archive-based landing pages.