Enhance E2E test to validate failed execution success field

[Copilot]

Proposed changes

The "Failed job execution has success=false" test in e2e/tests/03_job_execution.bats was only checking that executions exist, not validating the actual success field value.

Enhanced test to assert execution failure:

• Added assertion that verifies success == false in execution response
• Follows same pattern as successful execution test using jq filtering
• Now properly validates both execution count and failure status

# Before: Only checked execution exists
count=$(json_array_length "$body")
[ "$count" -ge 1 ]

# After: Also validates success field
failure_count=$(echo "$body" | jq '[.[] | select(.success == false)] | length')
[ "$failure_count" -ge 1 ]

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.