Multiple evolution method complications

[Cat333Pokemon]

Having support for multiple evolution methods causes the following complications:

• Items that don't exist in earlier generations may be flagged as appropriate methods
• Defining methods by generation would generally solve many issues, however...
• Different forms may evolve with different methods. In the relevant later games this could cause complications when importing, say, a Kantonian Vulpix into a game that only has Ice Stones. (This scenario is fictitious but likely exists with other Pokémon.)

[Cat333Pokemon]

Use the variableEvolutions() function for special cases. Notable ones include Eevee and Feebas, then forms start in Gen 7. Here are all of the ones that have multiple evolution methods for the same Pokémon:

 19: Rattata    -> Raticate
 27: Sandshrew  -> Sandslash
 37: Vulpix     -> Ninetales
 52: Meowth     -> Persian
 79: Slowpoke   -> Slowbro
 79: Slowpoke   -> Slowking
 82: Magneton   -> Magnezone
104: Cubone     -> Marowak
133: Eevee      -> Leafeon
133: Eevee      -> Glaceon
133: Eevee      -> Sylveon
299: Nosepass   -> Probopass
349: Feebas     -> Milotic
554: Darumaka   -> Darmanitan
737: Charjabug  -> Vikavolt
739: Crabrawler -> Crabominable
744: Rockruff   -> Lycanroc
891: Kubfu      -> Urshifu

There might be more that I'm missing, especially in Gen 9.