Improve logging for starting jobs and test cleanup

[AlanCoding]

SUMMARY

This is a mop-up of any remaining issues I saw while trying to do performance testing related to dispatcherd.

We had a case where scale-ups could result in missed messages, making these messages really important. Although the lost messages were recovered, it was still a pretty bad bug. It should be fixed now, but the logs are also valuable to keep.

This also adds some re-scheduling logic, which is going off of a gut intuition more than anything else. This did not ever cause a delay in job starting, and in practice it was always quite fast.

ISSUE TYPE

• Bug, Docs Fix or other nominal change

COMPONENT NAME

• API

---

Note

Improves job start behavior and observability while tightening test setup.

• Batch dispatch: dispatch_waiting_jobs now processes up to 25 waiting jobs per run, logs job IDs and elapsed time, and re-schedules itself if multiple jobs were dispatched; logs when none are available
• Test adjustment: test_bulk_job_launch_queries uses override_settings(BULK_JOB_MAX_LAUNCH=...) to ensure launches respect the configured limit

^{Written by Cursor Bugbot for commit 4b1cc69. This will update automatically on new commits. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud