Derive and render the Stable Address, and resolve every dependency coordinate to it #331

Parent

#324

What

Derive and render the Stable Address (chapter 16, 0093):

• one per surface an edge names, or whose Stable Address a tier's forward-auth endpoint is: <application>-<surface> in estate-system;
• ${dependency:<application>.host} resolves to <application>-<surface>.estate-system.svc.cluster.local, .port to the surface's port;
• the estate-scoped artifact renders each as an ExternalName Service whose target is the active Instance's Service (or a provider's recorded address), created once and never updated by Flux;
• every worked example's oracles whose coordinates change are rewritten by hand and reviewed.

Lands in TypeScript only, after emf/ is deleted (#347), with the rendered-tree and diagnostics oracles it affects, in one pull request. The intent, effective and dependencies goldens are dropped (#346), so it adds none.

Behaviour (draft ledger row)

A consumer's rendered coordinates name its provider's Stable Address and nothing about where the provider runs, and the estate-scoped share renders one ExternalName per named surface, targeting its active Instance.

Blocked by

#341, the map whose rewrite plan replaces the closed placement ticket #328 (see #350).