When reporting is not enabled, the resultsdb directive currently exits with a message saying that reporting is not enabled.

While this is expected behavior, it isn't incredibly helpful for the use case where someone is writing a task and testing it locally. We could add instructions for setting up a local resultsdb but that doesn't follow along with our strategy of making task writing mostly painless.

In the case where resultsdb reporting is not enabled, iterate through the input TAP and check to make sure that it is valid and contains all the items required for resultsdb reporting.