Age class as individual component

@mlange wrote: It looks like most of your systems have some condition regarding age class. It might be worth considering to have age classes as components for more efficient filtering. You would not only benefit from fewer entities to iterate in these queries, but also from less branching, which should improve cache prediction and thus data throughput.

There is a tradeoff depending on how long cohorts stay in each class, or rather on how often age class components would be exchanged. So in case you give it a try, start with setting up benchmarks for the full model so you are able to compare performance before/after.