Flight Spice IA code review changes (continued from #1187, #1268)

@moollaza Thanks for the comments and suggestions. I made most of the changes that you mentioned, but I have two questions. Regarding tests, I agree that we can just ignore the dates and just check that the city codes are correct. But, I don't know how to tell the test script to ignore the dates? And, regarding the simplification for breaking up the query that you suggested, I think that I am already doing steps 1 and 2 in the main function that handles the initial query? The subfunction just parses the remaining string that is either "city airline" or "airline city" for both codes, and there may be multiple words for both the city and the airline. Any suggestions for how to simplify the subfunction further?

@chrismorast Made the -0.2 em change. Here's a screenshot to compare:
![screen shot 2014-11-17 at 11 48 03 pm](https://cloud.githubusercontent.com/assets/5326740/5090794/9d843cf8-6f12-11e4-8f30-a134ab0b861a.png)

/cc @jagtalon @mwmiller @mintsoft Just keeping you updated with the new pull request...
@moollaza I placed the return at the bottom because this function needs to potentially check other endpoints if there are multiple airports first; if we place the return at the top, we won't necessarily catch all airports if the first result is empty.