Fix the hooks ordering issue that caused failed test to be reported as passed

[nprizal]

#44 introduced a bug where failed tests are reported as passed. This happened because I moved the execution collection (i.e. adding it to payload) from after call to after teardown lifecycle. Apparently, the pytest_runtest_logreport hook that called after teardown return a report object that contains the outcome of teardown process, not the outcome of the test call. Therefore, when the test call result is failed, it is reported as passed because the teardown process was successful.

This PR address the issue by fixing the hook ordering to be:

pytest_runtest_logstart:
  create test data and store it to `in_flight` object
pytest_runtest_setup:
  -
pytest_runtest_call:
  -
pytest_runtest_logreport (only after call):
  collect the test result and update the test data
pytest_runtest_teardown:
  collect the execution tags
  add test to payload

[zhming0]

Interesting! Looks good 👍🏿 . But since we cannot easily write a test for this, it's probably better to add more code comments for future travellers.