Move bot recon superjump from TacticalMonitor to MainAction

[sunzenshen]

Description

Before, the decision for a recon jump was tied up with the single threaded execution of CNEOTacticalMonitor. That meant that when the bots were occupied with any other behavior associated with TacticalMonitor such as retreating to cover or avoiding grenades, the bots would not consider super jumping. By moving the implementation to CNEOBotMainAction, the Recon bots will always consider super jump no matter what scenario or tactical monitor behavior the bots are currently engaging in.

Toolchain

• Windows MSVC VS2022

[sunzenshen]

Before and after footage, though sometimes the behavior is tricky to trigger, especially if one accidentally triggers the behavior too early, such as by setting a nearby waypoint that exceeds the jump distance threshold, or when ordering the bots to follow:

bot-recon-superjump-any-scenario.mp4

The following console commands may be helpful for testing:

sv_neo_bot_cmdr_enable 1;
sv_neo_bot_cmdr_debug_pause_uncommanded 1;
neo_ctg_round_timelimit 99;
bot_class 0;
neo_bot_recon_superjump_min_dist 1000;

(I've been debating whether to increase neo_bot_recon_superjump_min_dist to reduce the occurrence of wasted nearby superjumps. Too large a value and the bots will not superjump to avoid quick reaction time scenarios like grenades, and too little the bots will jump too much for suboptimal situations.)