fix: expose scenario name in $test binding

[Ayush-Patel-56]

Explanation

Scenario names were silently ignored at runtime - defining a name on a scenario had no effect beyond the YAML schema. This fix makes the name available as $test.ScenarioName so it can be referenced in bindings, scripts, and expressions.

Related issue

Fixes #2614

Proposed Changes

• Added ScenarioName string to TestInfo in pkg/runner/info.go
• Passed scenarioName into setupTestContext so it gets populated in the $test binding

Checklist

• I have read the contributing guidelines.
• I have read the PR documentation guide and followed the process including adding proof manifests to this PR.
• This is a bug fix and I have added unit tests that prove my fix is effective.

Further Comments

Before this fix, $test.ScenarioName was always an empty string even when name was set on a scenario:

{"Id":1,"ScenarioId":1,"ScenarioName":"","Metadata":{"name":"scenario-name-test"}}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.71%. Comparing base (d253bff) to head (ba6e4bf).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2705   +/-   ##
=======================================
  Coverage   67.70%   67.71%           
=======================================
  Files         149      149           
  Lines        5757     5758    +1     
=======================================
+ Hits         3898     3899    +1     
  Misses       1599     1599           
  Partials      260      260           

☔ View full report in Codecov by Sentry.
📢 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.

[eddycharly]

Coming back to this, I wonder why we don't have a ScenarioInfo struct 🤔