Bot CTG gameplay behaviors

[sunzenshen]

Description

Bot behaviors for playing CTG mode.

Toolchain

• Windows MSVC VS2022

[sunzenshen]

This is why I changed the SAFEST_ROUTE parameters for other path calculations not related to the ghost. There wasn't any existing handling with this case beyond some stubs related to combat areas, so this was the cleanest way I could think of for choosing paths as a ghoster team.

[sunzenshen]

See neo_bot_path_cost.cpp for why these route type changes.

[sunzenshen]

Rebased on top of the bot command branch, so now the following debug commands are available:

sv_neo_bot_cmdr_enable 1;
sv_neo_bot_cmdr_debug_pause_uncommanded 1;
neo_ctg_round_timelimit 99;

This PR doesn't really need bot commands for testing, but might be worth thinking of test scenarios where the CTG behaviors and bot commands may interact.

I guess one possible interaction to look into after a first pass of feedback is that a bot holding the ghost will not report enemy positions to teammates, as they will be in the follow behavior. Maybe I should move the enemy reporting code into neo_bot_tactical_monitor and make it a general behavior to report ghoster targets (if the bot has the ghost equipped), instead of making it limited to the ghost carrier behavior.

[sunzenshen]

I guess one possible interaction to look into after a first pass of feedback is that a bot holding the ghost will not report enemy positions to teammates, as they will be in the follow behavior. Maybe I should move the enemy reporting code into neo_bot_tactical_monitor and make it a general behavior to report ghoster targets (if the bot has the ghost equipped), instead of making it limited to the ghost carrier behavior.

I ended up refactoring the ghost callout logic into a publicly accessible helper function so that the bot commands follower behavior can reuse the same routines.