Recover partial Azure function indexing

[jeremydixon22]

Summary

• detect a stable partial runtime inventory after Flex One Deploy
• issue one bounded Function App restart, which triggers Azure's background trigger synchronization
• retry the exact package-derived runtime inventory after recovery
• record whether recovery was attempted in the redacted receipt
• bound each runtime inventory request and shorten the overall discovery window
• cover immediate success, empty inventory, persistent partial indexing, and restart recovery deterministically

Why

A disposable hosted run completed One Deploy successfully but remained on a one-of-seven runtime inventory. The app was fully deleted by the existing cleanup path. This change treats that state as a recoverable Flex indexing race once, while persistent mismatch remains a hard failure.

Verification

• deterministic Azure gate harness, including restart recovery and persistent failure
• complete disposable managed-Azure qualification with exact inventory, ordinary execution, external-event wait, durable timer, live state assertions, redacted receipt, and full cleanup
• pre-merge release boundary and release-mode public export/history/ownership/credential/secret checks