/query: finish implementation

[kevinlul]

Per #342, this is intended to succeed old Bastion .match and .search. Lucene queries are more powerful than the ygo-data filter system and require no additional implementation effort.

Simple query strings are also possible for most search cases but are not implemented here as they cannot search on arbitrary fields. In context, only about 3% of .match and .search invocations applied additional filters on card properties rather than just searching text.

[kevinlul]

A lot of field aliases will be needed for nice native-language support, e.g. 이름 for name.ko. Other cases: link and link_rating, race, breaking up monster_type_line.