Because this affects more than just the template insights page (specifically it also affects the deployment stats endpoint which is shown on bottom bar and Prometheus), the group is being renamed generically to just "stats". In the future if we need to affect all stats or the other stats we can put those options here.

Then, because this flag only affects a portion of stats, specifically usage stats like connection and application time, bytes sent, etc, add a new sub-group called "usage".

Then finally add back the "enable" flag. This also gives us a place to one day place an "anonymize" flag if we need to go that route.

What do y'all think? One unfortunate thing about this name is that--stats-usage-enable kind of sounds like "enable the usageof stats" rather than "enable the collection of usage stats". But if I flip it around likeusage-stats-enable then there is no longer a section that can affect all stats, not just usage stats, if we need that one day (but maybe we will never need that):

usageStats:  enable: boolean

We could maybe do something like have two vars that separately control the agent and app stat tables, but although that lines up nicely code-wise, not sure it would make sense to a user unless they know what the database schema looks like (of course the descriptions would help though):

stats:  agent:    enable: boolean  app:    enable: boolean