There are some places across the code base where cognitive overhead could be decreased by grouping functions that are spread across a class, but perform similar tasks, into a new utility class.
Similarly, some inner classes or enums with fields that are initialized once and queried once afterwards could also be moved into their own class.
Annotation handling and BiGGId creation is now properly centralized and inner classes moved out to their own proper class.
I'll close this for now, as most major offenders should now be dealt with.
There are some places across the code base where cognitive overhead could be decreased by grouping functions that are spread across a class, but perform similar tasks, into a new utility class. Similarly, some inner classes or enums with fields that are initialized once and queried once afterwards could also be moved into their own class.