Describe the bug

Attempting to rerun a job with the job ID (as shown in the .../actions/runs/<run-ID>/job/<job-ID> URL) using the gh run rerun -j <job-ID> command throws a 404 error no matter the token used. However, gh run rerun <run-ID> works as expected.

CLI info:

gh version 2.20.0 (2022-11-08)

Steps to reproduce the behavior

1. Type gh run rerun -j <job-ID> with any valid job ID
2. See error: failed to get job: HTTP 404: Not Found (https://api.github.com/repos/superblocksteam/superblocks/actions/jobs/<job-ID>)

Expected vs actual behavior

I expect the rerun of the job to work, but what actually happens is that I get a 404.

It is also unclear why specifying a run ID and a job ID (which exists in the run) together aren't valid - gh run rerun <run-ID> -j <job-ID>.

Logs

❯ gh --version
gh version 2.29.0 (2023-05-10)
https://github.com/cli/cli/releases/tag/v2.29.0

❯ gh run view 5107576769 --json jobs | jq -r '.jobs[] | select(.name == "allow-merge") | .url | capture("/jobs/(?<job_id>[^/]+)$") | .job_id'
9180945000

❯ gh run rerun -j 9180945000
failed to get job: HTTP 404: Not Found (https://api.github.com/repos/superblocksteam/superblocks/actions/jobs/9180945000)

Run and job IDs together:

❯ gh run rerun 5107576769 --job 9180945000
specify only one of `<run-id>` or `--job`

Usage:  gh run rerun [<run-id>] [flags]

Flags:
  -d, --debug        Rerun with debug logging
      --failed       Rerun only failed jobs, including dependencies
  -j, --job string   Rerun a specific job from a run, including dependencies