Handle new run-log structure for repo-level runners

[AdnaneKhan]

It appears that repo-level runners show up a bit differently in run logs.

The logs no longer specify it as a repo-level runner, and the startup info is now in a system.txt within the zip directory.

Example for repo-level:

2025-04-17T00:28:38.7203674Z Requested labels: self-hosted, e2, cpu
2025-04-17T00:28:38.7203674Z Job defined at: AI-Hypercomputer/maxdiffusion/.github/workflows/UploadDockerImages.yml@refs/heads/main
2025-04-17T00:28:38.7203674Z Waiting for a runner to pick up this job...
2025-04-17T00:28:39.2354756Z Job is about to start running on the runner: maxdiffusion-github-docker-build-runner

Example for org-level:

2025-04-16T17:04:45.0888998Z Requested labels: self-hosted, linux, spellbook-trino-ci
2025-04-16T17:04:45.0889436Z Job defined at: duneanalytics/spellbook/.github/workflows/commit_manifest.yml@refs/heads/main
2025-04-16T17:04:45.0889593Z Waiting for a runner to pick up this job...
2025-04-16T17:04:45.3376340Z Job is about to start running on the runner: github-runner-trino-spellbook-ci-prod-0 (organization)

Update Gato-X to process the repo level case by parsing the system.txt (so it doesn't miss the labels), also treat the lack of a group and org designation as an indication it is a repo level runner.