Fix pytest.fail() not captured in cucumber JSON step output

[jackhenderson101]

pytest.fail() raises _pytest.outcomes.Failed which inherits from BaseException, not Exception. The except Exception handler in _execute_step_function was bypassing the pytest_bdd_step_error hook, leaving the step's failed flag as False and causing all steps to appear as "passed" in the JSON output even when the test failed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.10%. Comparing base (9454b38) to head (a77484e).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #811   +/-   ##
=======================================
  Coverage   96.10%   96.10%           
=======================================
  Files          55       55           
  Lines        2390     2390           
  Branches      136      136           
=======================================
  Hits         2297     2297           
  Misses         56       56           
  Partials       37       37           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[hiSandog]

Capturing pytest.fail() in cucumber JSON is the right direction, but the edge case is hook ordering around step teardown. It would be good to include a scenario where pytest.fail() happens inside the step body and another where failure is raised from a fixture/teardown path, then assert the JSON has the failed status and useful message in both cases. That keeps the report format reliable for CI consumers.