[Warden] Warden control scripts do not target PlanetsLib variants of the Warden

This update concerns the latest Muluna update(2.6.0) and how it interacts with script-driven entities like the Warden. Muluna uses the PlanetsLib entity replacement system to create copies of every vehicle that consumes chemical fuel, and changes fuel categories only on Muluna. For all intents and purposes, the variant vehicles are the same as the original vehicles, in all but internal name. This is a problem for any control scripts that use hardcoded names, such as those used by Warden.

To fix: Add all values from PlanetsLib.constants.entity_variants_list.warden(Or prototypes.mod_data.Planetslib.data.entity_variants_list.warden) to the list of entity names that should be seen as Wardens for the purpose of Warden's control scripts. Do the same for all other entities with control scripts that use hardcoded names.

Start by locating Warden's control scripts and the other control scripts that use hardcoded entity names. Read the PlanetsLib entity_variants_list.warden entry, then identify the corresponding variant lists for other scripted entities. Done means every relevant PlanetsLib variant is recognized by the appropriate control script.

Written by the indexing model from the issue text.