Gracefully return a NoResultsWarning and empty table

We recently saw a few regressions that result from not properly handling empty query returns. I would be useful to go through the modules and double check that the result parsing methods are not choking on empty results.

Recent examples #1836 and #1829

Start by reviewing regressions #1836 and #1829, then inspect the result-parsing methods across the affected modules. The work is done when empty query returns are handled consistently by returning a NoResultsWarning and an empty table without raising parsing errors.

Written by the indexing model from the issue text.