Startup now explicitly waits for the policy-limits verdict

What

Startup code that depends on organization policy limits (restrictions your admin can configure) now goes through a new awaitColdStartVerdict()/bin() wait-with-timeout pair instead of the old load-and-wait routine.

• The old startup routine, which called ensureLoadRequested/waitForLoad with a timeout and recorded completed/timed_out outcomes, was replaced with a simpler skip-check plus the new wait call.
• The MCP (Model Context Protocol) cold-start sequence now waits up to a budget for the policy-limits verdict before expanding server config variables, logging if it times out and falling back to loading MCP configs without the verdict.
• The wait records whether it completed or timed_out and reports its duration via a new metric.

Why

This makes sure organization policy restrictions are known before dependent startup steps (like loading MCP server configs) proceed, while still timing out gracefully instead of hanging startup if the check is slow.