fix(pak): install deferred culprits in dependency order + retry pass

[eliotmcintire]

Symptom

Under Require.noRemotes = TRUE (Linux, R 4.6), the install ended with:

ℹ Building LandR.CS 2.0.0.9006
✖ Failed to build LandR.CS 2.0.0.9006
...
✔ Installed LandR 1.2.0.9002 (github::PredictiveEcology/LandR@f9d7d39)
=== Install summary: 1 package(s) not installed ===
  LandR.CS  [build-error]  dependency 'LandR' is not available for package 'LandR.CS'

LandR.CS Imports LandR. Both were deferred build-failure culprits, and the identify-and-defer final serial phase installed them in deferral order — so LandR.CS was built before LandR, failed its R CMD INSTALL pre-flight dep check, and was never retried once LandR landed.

Fix

1. orderRefsByMissingDepEdges() — topologically order deferred culprits using pak's own dependency 'X' is not available for package 'Y' lines (Y depends on X), so X installs before Y. Index-based + stable; bails out of cycles without dropping refs; handles curly- and straight-quote messages.
2. Retry pass — after the serial install, re-attempt still-missing culprits while progress is being made (a dependency installed late in the pass unblocks its dependent). Stops as soon as a pass makes no progress (≤ 3 passes).

Regression test added (orderRefsByMissingDepEdges: dependency ordered before dependent; no ref dropped; unrelated/foreign edges leave order intact). Bump 2.0.0.9034 → 2.0.0.9035.

Note: separately, that LandR built from GitHub under noRemotes = TRUE suggests LandR.CS's internal Remotes: is being followed during its source build (bypassing the r-universe resolution noRemotes intends). That's a distinct noRemotes-completeness question, not addressed here.

🤖 Generated with Claude Code