Fix firewall parser to use setupGlobals pattern

[Copilot]

The firewall log parser step was calling main() with parameters instead of using the setupGlobals() pattern, causing the parser to fail when accessing core as a global variable.

Changes

• Updated generateFirewallLogParsingStep() in pkg/workflow/copilot_srt.go to call setupGlobals() before requiring the parser script
• Changed main() invocation to match agent log parser pattern (no parameters)

Before

const { main } = require('/tmp/gh-aw/actions/parse_firewall_logs.cjs');
await main({ github, context, core, exec, io });

After

const { setupGlobals } = require('/tmp/gh-aw/actions/setup_globals.cjs');
setupGlobals(core, github, context, exec, io);
const { main } = require('/tmp/gh-aw/actions/parse_firewall_logs.cjs');
await main();

This aligns with how all other log parsers (Claude, Codex, Copilot) access GitHub Actions objects as globals.

Original prompt

Reference: https://github.com/githubnext/gh-aw/actions/runs/20515319042/job/58942042783#step:45:1

Fix firewall parser JavaScript to use require and setup globals

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.