Applies the resolution tiers and returns the limits that actually apply,
with the tier that supplied each axis. Use this rather than the raw GET
when you want to know what is in force, or to confirm an override took
effect.

Resolution is axis-by-axis:

• node-wide axes come from the node row only — there is no per-user
  override for what the whole node may spend
• per-user axes: user override → node default → unlimited

configured: false means the node imposes no pipeline ceilings at all,
the normal state for a customer-owned node.

Note: this reports limits only, not spend. The pipeline usage table
is owned by workflow-service, so remaining allowance comes from
GET /compute-nodes/{nodeId}/budget there — which resolves with the
same logic the run gate enforces, so the two cannot disagree.

Permissions: node and default stay owner-only. A user may read
their own scope (pass me) if they have access to the node.