Add dependency-aware async initialization to the container

Normalized profile

What this task asks for

Add dependency-aware asynchronous container initialization with ordered startup, concurrency limits, and rollback on failure. Add support for asynchronous initialization of container registrations with automatic dependency-aware startup ordering. If any initializer throws or rejects, the container calls `dispose()` on all already-initialized services (in reverse order). The initialization respects the dependency graph by organizing services into "levels", all services at level N must complete before level N+1 begins. Services without initializers can be resolved before `initialize()` is called. The initializer function receives the resolved instance and may return a replacement. Circular dependencies detected during initialization graph construction must throw AwilixResolutionError, and such graph-build failures must not transition the container into a failed state, allowing initialize() to be retried.