Coordinate playerbot hunt workflows

[adrunkhuman]

Summary

• Own combat, corpse-loot, hunt planning, patrol, and shared cooldown state in PlayerBotHuntCoordinator.
• Centralize cross-workflow kill, danger, death, patrol, and turn-observation transitions while PlayerBotController retains scheduling, lifecycle, player lookup, world actions, and turn dispatch.
• Document the ownership and side-effect boundary.

Verification

• docker compose -f server/compose.yaml build server - passed
• Focused planning, patrol, pursuit, corpse-loot, and death scenarios - 8/8 passed

Notes

Service, depot, and progression remain in PlayerBotController because they still share its navigation and lifecycle concerns; this extraction did not produce a useful common boundary for them.