fix(kode-bayar): move collector links into the existing quick menu ## Changes Government kode-bayar details rendered a collapsed extra Menu Cepat card above the payment details, leaving a large blank area. Move Ubah Pemungut or Riwayat Pemungut into the existing sidebar Menu Cepat card, preserving eligibility checks and destinations. Closes #1886 ## Release impact Patch. Restore the intended placement of existing navigation links without introducing a new capability. ## Migration notes No schema, configuration, or data migration is required. ## Validation - Passed UI policy checks: `pnpm check:ui --base dfd5577ffde8ad40f50911df42a330d51176fa30`. - Passed ESLint for all three changed files. - Passed `pnpm check:react-doctor:changed --base dfd5577ffde8ad40f50911df42a330d51176fa30` with zero errors, zero warnings, and no incomplete checks. - Confirmed the original production card had zero width and a height of 1,831 pixels. The updated page has not been verified in a running app. - Build, test, and dev commands were not run, as instructed. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Updates** * Collector-related quick links are now shown in the important information card on the payment code page, alongside existing payment links, rather than in the page navigation. * The card can display additional quick actions when provided. When none are provided, its existing links remain unchanged. <!-- end of auto-generated comment: release notes by coderabbit.ai --> fix(feedback): prevent new reports starving in GitHub sync New bug reports and suggestions can stay at GitHub "Menunggu" indefinitely because PostgreSQL sorts NULL scheduled times after dated polling work. Recurring polls and repository-wide PR webhook wakeups keep that dated backlog ahead of reports that have never been attempted. Select eligible NULL scheduled times first, retaining the ID tie-breaker, retry delays and active leases. Add regression coverage for both report kinds with a polling backlog larger than the batch, an active lease and a future retry. ## Validation - Read-only production queue comparison reproduced the old ordering skipping reports 71 and 73 and the corrected ordering selecting both. - TypeScript syntax, Prettier and git diff checks pass. Independent diff review found no actionable issues. - Regression tests added but not run. Build, tests and dev commands were not run, per the user's instructions. ## Recovery and rollout Requeued production reports 71 and 73 through the existing worker. Their issues are #1886 and #1887. Both saved synced revision 1, matching their report revision, with no sync error. Production had zero unlinked bugs or suggestions after recovery. The queue ordering fix still needs release through the normal production flow. No migration or configuration change is required. ## Release impact Patch. Restore the existing GitHub feedback synchronization behavior.