chore: re-trigger CodeQL after GitHub 503 incident

Prior default-setup CodeQL init failed on transient GitHub API 503s. Retrying now that the API has recovered.

Assisted-by: GitHub Copilot (model: Claude Opus 4.8, autonomous)

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 20f1fc64-ba5b-4f3d-82af-855c43952ab3

Author: mnriem