fix: e2e_report_steps must use same path pattern as step tracking functions

The bug: e2e_step_start/end write to absolute paths based on REPO_ROOT,
but e2e_report_steps was reading from relative 'reports/steps'.

Result: Steps ran and wrote status files, but summary couldn't find them,
reporting 'Step never executed' even for successful steps.

Fixed by:
- Update e2e_report_steps to use same path: ${E2E_STEPS_DIR:-${REPO_ROOT:-.}/reports/steps}
- Update diagnostic logs path for consistency
- Remove unused _step_dir variable from build-node

This ensures both writing and reading use the same absolute paths.

Author: abueide

examples/react-native/tests/test-suite-ios-e2e.yaml

@@ -59,8 +59,6 @@ processes:
     command: |
       set -e
       _step="build-node"
-      _step_dir="reports/steps"
-      mkdir -p "$_step_dir"
 
       # Source test framework for timing functions
       export REPO_ROOT="$(cd ../.. && pwd)"

plugins/tests/test-framework.sh

@@ -258,7 +258,7 @@ e2e_step_end() {
 # failures with "Step never executed". This catches false successes where
 # processes are skipped due to broken dependency chains.
 e2e_report_steps() {
-  local steps_dir="reports/steps"
+  local steps_dir="${E2E_STEPS_DIR:-${REPO_ROOT:-.}/reports/steps}"
   local any_failure=0
   local expected_steps=("$@")
   local found_steps=()
@@ -336,7 +336,7 @@ e2e_report_steps() {
 
   # List available diagnostic logs when there are failures
   if [ "$any_failure" -eq 1 ]; then
-    local logs_dir="reports/logs"
+    local logs_dir="${E2E_LOGS_DIR:-${REPO_ROOT:-.}/reports/logs}"
     local has_logs=0
     for logfile in "$logs_dir"/*.log "$logs_dir"/*.txt; do
       [ -f "$logfile" ] || continue