Sharing private worker pools across spaces without inheritance

Workaround

No

Problem

Worker pools are currently scoped to a space and can only be shared via space inheritance (parent > child). This creates a few issues: - Sibling spaces cannot share worker pools directly. - Sharing requires introducing a parent space purely for resource distribution. - Inheritance must be enabled, which is not always desirable. In some setups, inheritance is intentionally disabled to maintain isolation between spaces (for example, to enforce separation between teams or environments). When inheritance is disabled, spaces lose access to shared resources entirely. This forces a trade-off between isolation and reuse.