feat(di): feature modules resolve shared/core deps (7.1.0)

[jacobaraujo7]

Release 7.1.0 — feature modules can consume shared/core deps

Closes the resolution asymmetry surfaced while reviewing a real v7 app: a
feature module's module-level binds could not resolve dependencies from a
root-owned shared/core module (a path-less module(...)). Only page-scoped
provide binds could reach the core; feature binds ran in a leaf injector blind
to root-owned binds — forcing shared deps to be threaded in by hand.

What changed

• _bind now composes the feature injector with auto_injector 2.2.0's
  opt-in upward resolution: root.addInjector(injector, resolveUpward: true).
• A core consumer can now be a provide, the core itself, or a feature
  module-level bind — all alike. A feature's own bind still shadows a
  same-typed core bind (local wins; core is the fallback).
• Constraint bumped to auto_injector: ">=2.2.0 <3.0.0".

Verified behavior (the gap, reproduced then fixed)

Bind site	Resolves a core (root-owned) dep?
Page-scoped provide	✅ before & after
Feature module-level addSingleton (eager)	❌ before → ✅ 7.1.0
Feature module-level add (lazy factory)	❌ before → ✅ 7.1.0
Feature module-level addLazySingleton	❌ before → ✅ 7.1.0

auto_injector 2.2.0 (dependency)

Adds addInjector(child, resolveUpward: true) (opt-in, default false — no
behavior change for existing users), fixes a dispose-listener accumulation in
its layer graph, and adds an UpwardResolutionCycle guard against mutual upward
links.

Tests

• New test/feature_resolves_core_test.dart regression test (feature
  module-level bind resolves a core ApiConfig).
• Full suite green (62/62), flutter analyze clean.

🤖 Generated with Claude Code