-Fixed Codex generation before requirements are met

-Delays the removal of the original followers until after the replacements have been generated.
-If not enough replacements have been generated to match the number of followers in the original pod, ignore it and leave the vanilla pod.
--This behavior is partially-configurable. The new bReplaceFollowersInPlace config flag will force the replacement followers in, replacing only as many followers as could be generated. For example, if the original pod had 5 enemies, and DAP could only generate 2 followers, it will replace the first 2 followers and leave the other 2, and leader, alone.

Now finds all lists corresponding to ListNameToUse when determining enemies to pick for a pod, as many lists appear multiple times in the same name. Should fix the game always picking enemies from the first list (e.g. always picking ADVENT Troopers from the list of DefaultFollowers)

-Fixed list generation to only use dark event lists if either: -the dark event doesn't care what the leader is, or -the dark event cares what the leader is, and the leader was chosen by the dark event.
--In plain english: If there's a dark event present but it didn't affect the pod's leader, DAP will no longer use the dark event to affect the pod's followers.

-Fixed handling for MaxCharactersPerGroup
-Forced to run after Increase Pod Size By Force Level, making the two compatible

-Moved pod emptying to after the check to see if the mod can add new followers, so if the answer to that question is "no," the original pod is left untouched. This should solve compatibility with mods like MOCX.
-Added boolean variable to control whether or not to ignore forced pod makeups. Forced pod makeups are not Diverse, but some mods rely on them, so it might be important if the previous change fails to be compatible with those mods.
-Added boolean variable to restrict followers to the same alien type of the leader. Requested by DerBK for ABA, roughly 502 years ago, and I finally got around to it because I suck.