mt-sync-code-data: auto-create issue on parse step failure

[Copilot]

When MT parse current or MT parse next fails, the workflow silently dies with no actionable follow-up. This adds automatic issue creation on failure for both parse steps.

Changes

• Step IDs: Added id: mt-parse-current / id: mt-parse-next to enable outcome checks
• Error handling steps (one per parse step): fire on failure() && steps.<id>.outcome == 'failure' and:
  • Fetch failed logs via gh run view <run_id> --log-failed
  • Create a Bug-type issue labeled bug, assigned to copilot, with:
    • Link to the failing run
    • Collapsible <details> block containing the raw failed logs
    • Fix instructions pointing to config/gtfs/*.json, *AgencyTools.java, and the parser repo
  • Post a follow-up comment @mtransitapps/reviewers please review on the created issue

- name: MT parse current failed - create issue
  if: ${{ failure() && steps.mt-parse-current.outcome == 'failure' }}
  run: |
    FAILED_LOGS=$(gh run view ${{ github.run_id }} --log-failed 2>&1 || echo "Failed to fetch logs")
    ISSUE_URL=$(gh issue create \
      --title "${STEP_NAME} failed" \
      --type "Bug" \
      --label "bug" \
      --body "${ISSUE_BODY}" \
      --assignee "copilot")
    gh issue comment "${ISSUE_URL}" --body "@mtransitapps/reviewers please review"
  env:
    GH_TOKEN: ${{ secrets.MT_PAT }}