Description

When large servers have high player event log volume, they can choose to offload player events to another server (QueryServ) where it has a separate logging database and server entirely.

The problem with this is that player event log settings can become split brained because the settings are authoritative on QS (log server). The zone server loads settings locally instead of pulling them from QS. This PR addresses that by having QS send settings when zone initially connects.

When #reload or Spire reload requests are issued, when the rule Logging:PlayerEventsQSProcess is enabled, zones will instead reload from QS instead of reloading from their local.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Testing

When zones boot, they fetch settings from QS when Logging:PlayerEventsQSProcess is enabled

This is when log settings are reloaded either from in game or from Spire

Checklist

• I have tested my changes
• I have performed a self-review of my code. Ensuring variables, functions and methods are named in a human-readable way, comments are added only where naming of variables, functions and methods can't give enough context.
• I own the changes of my code and take responsibility for the potential issues that occur