Dialogue: Support for Pilot Dialogue to handle non-Player Lances

[redbatz]

Currently the Dialogue System only support pilots from player lances, which limits the dynamic interactions to only between predefined cast of other teams.
Adding support for pilots from all the other teams would be useful to create both more immersive storylines and reactive dialogue from other teams.

Key Goals

• Same core functionalities as for player lances is the goal, including True/Bound Random, Specific Position, etc.
• Only spawned and alive pilots should be selectable. Any references to dead or not yet spawned units should have fallbacks and be handled gracefully.
• For non-friendly teams, sensor information might be limited and reduce selectable scope. Can possibly be configured through conditionals to allow open or only known communication sources.
• If no selectable pilot is found, an Unknown radio source might be used as fallback.

Considerations

• Should visibility matter? Or just Sensor information?
• Once a pilot's information has been detected, should it be remembered? Or does losing sensor information mean you don't know the source of transmission? Not sure how it works in universe.
• Should additional lances be considered as possible targets?

Stretch Goals

• Configurable integration with LowVisibility to retrieve knowledge level of sensors.
• More conditionals could be interesting. Maybe related to Mech status if possible?

[CWolfs]

This all sounds good to me.

Just a point to consider for the LowVis stuff - MC doesn't link against other mods to keep it as widely compatible as possible so if it requires linking against the LowVis .dll then it's a no-go (unless you have checks for dlls existing etc like some mods do).

After our discussion in Discord, I'm thinking the sensor information might be less important than I originally thought it should be. Probably something to consider but no need to let it get in the way of the main features.