Monster flag usage frequency

[ZhilkinSerg]

Summary

SUMMARY: Infrastructure "Monster flag usage frequency"

Purpose of change

Allow gathering statistics on accessing various monster flags.

Describe the solution

Added gathering of monster flag usage statistics.

Additional context

Current PR would allow gathering monster flag usage statistics, so we could later move frequently accessed flags to monster type class fields.

Data can be dumped to debug.log through "Game State" debug menu. Data is sorted by usage count in descending order. Data format is the following (can be directly inserted to spreadsheet apps):

12:46:05.020 INFO : Monster flag usage statistics:
FLAG	COUNT
DIGS	197538
CAN_DIG	179449
SEES	90291
FLIES	89965
CLIMBS	74235
SUNDEATH	59921
AQUATIC	57146
NIGHT_INVISIBILITY	45540
NO_BREATHE	42079
REGENERATES_50	41837
REGENERATES_10	41837
REGENERATES_1	41832
REGENERATES_IN_DARK	41832
REGEN_MORALE	41832
ELECTRIC_FIELD	41832
SWIMS	39035
RIDEABLE_MECH	30140
ABSORBS	30097
ABSORBS_SPLITS	30097
SWARMS	30097
GROUP_MORALE	30097
PRIORITIZE_TARGETS	30097
STUMBLES	30096
IMMOBILE	30096
CAN_OPEN_DOORS	30096
SMELLS	30092
KEENNOSE	20231
PATH_AVOID_DANGER_1	18089
PATH_AVOID_DANGER_2	18089
PATH_AVOID_FIRE	18089
PATH_AVOID_FALL	18089
ACIDTRAIL	17801
SHORTACIDTRAIL	17801
SLUDGETRAIL	17801
DRIPS_NAPALM	17801
DRIPS_GASOLINE	17801

I will move most offending flags into monster/mtype properties in separate pull requests like #35775.

[BevapDin]

Why even keep the bitset? Why not just the boolean members? We usually check for flags that are known at compile type.

[ZhilkinSerg]

Why even keep the bitset? Why not just the boolean members? We usually check for flags that are known at compile type.

That is the intention - find which flags are accessed often and have replaced them with boolean members. Changing this immediately would required bigger changes both to code and json and I am trying to avoid it for now.