hack/devnet: wire buildoor inventory into generated dora config

[barnabasbusa]

Summary

Mirrors the validator-names pattern in run.sh so `make devnet` produces a generated dora config with `buildoorOverviewUrl` / `buildoorUrls` set automatically.

• Named devnet (`network: ` in the kurtosis config) → `buildoorOverviewUrl: https://buildoor..ethpandaops.io` is emitted alongside the existing `validatorNamesInventory` for the same network.
• Local kurtosis buildoor (`mev_type: buildoor`) wins over the network-derived URL. The script discovers the `buildoor` enclave container, reads its host-published port for container port 8080, and emits `buildoorUrls: ["http://127.0.0.1:"]`.
• Otherwise (named non-devnet network, no local buildoor) → `${BUILDOOR_CONFIG}` expands to empty and the line is dropped.

Both modes drop a single line into the generated `frontend:` block — exactly the same plumbing model as `${VALIDATOR_NAMES_CONFIG}`.

Test plan

• `make devnet` against a `network: glamsterdam-devnet-5` config → generated `frontend.buildoorOverviewUrl` points at the live overview.
• `make devnet` against a local `mev_type: buildoor` config → generated `frontend.buildoorUrls` lists `http://127.0.0.1:`.
• `make devnet` against a vanilla local devnet (no buildoor) → no buildoor line in the generated config.
• After `make devnet-run`, dora logs `buildoor inventory refreshed: N resolved, M unresolved` on the refresh interval; slot bids view shows the external-link icon.