Consider Angular-style `inject` functions in injection contexts

This would likely be a large change.

Angular keeps track of injection contexts by keeping a "stack" of contexts. It is a synchronous system. Running in an injection context involves assigning a global variable as part of a wrapper function.

For example, Something like `runInInjectionContext(yourCallback, injector)` would populate a global variable `CURRENT_CONTEXT` to define the injection context. All code running inside the callback `yourCallback` would have access to that context. Once the `yourCallback` returns, the wrapper function `runInInjectionContext` would destruct the context, essentially assigning the global `CURRENT_CONTEXT` to something like `undefined`.

There could potentially be more involved ways to keep the injection context non-global, such as using some sort of function symbol or modifying function prototypes, but that can get messy. Perhaps traversing up a `caller` chain could also do this as well.

The issue describes adding Angular-style injection contexts. Start by examining the existing injector and dependency injection mechanisms in the codebase. Look for how contexts are currently managed and where a global or call-stack based context could be integrated. Understanding the synchronous wrapper pattern and the potential impact on the framework's architecture is key.

索引モデルが issue の本文から書いたものです。