More trivial updates - /dexsearch and /intro

@Slayer95 jsyk I'm reverting part of your dexsearch optimisation because, while your update was correct and slightly faster, this way ensures accuracy at the cost of minimal speed (it prints the results in pokedex order instead of the order they were in the dex object, which has an effect where movepool problems occur, such as /dexsearch dragon rage, blast burn - your way has Charmeleon last (after Zard/Zard-X/Zard-Y/Smeargle) where it should be between Charmander and Charizard, as this method places it). Perhaps the accuracy is not /that/ important but I'm somewhat of a pedant