Update dependency get_it to v9

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
get_it	dependencies	major	^8.0.3 -> 9.1.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

flutter-it/get_it (get_it)

v9.1.0

Compare Source

• Added DevTools extension for visualizing and inspecting GetIt registrations
  • View all registered objects with their type, scope, registration mode, and state
  • See instance details via toString() output for created instances
  • Manual refresh button to update the registration list
  • Requires debugEventsEnabled = true to be set on GetIt instance
  • See README for setup instructions

v9.0.5

Compare Source

• Use absolute GitHub URL for logo in README

v9.0.4

Compare Source

• Fixed screenshots description to match working 9.0.1 format

v9.0.3

Compare Source

• Fixed logo display on pub.dev by using relative path

v9.0.2

Compare Source

• Fixed button sizing in README for pub.dev display

v9.0.1

Compare Source

• Fixed linter error (missing trailing comma in test file)

v9.0.0

Compare Source

• BREAKING: Disposal order now always follows strict LIFO (Last-In-First-Out) based on registration order
  • Previously, disposal order was based on the order objects appeared in internal hash maps, which was unpredictable when mixing named and unnamed registrations
  • Now all disposals are sorted by registrationNumber (a sequential counter assigned during registration) ensuring true LIFO order
  • The strictDisposalOrder parameter has been removed from reset(), resetScope(), popScope(), popScopesTill(), and dropScope() methods
  • Performance impact is minimal: ~8% overhead for 10,000 registrations (approximately 2-3ms), negligible for typical applications
  • This change ensures correctness and predictability in dependency cleanup, which is more important than the minor performance cost
  • Impact on existing apps: If your app's behavior relies on the previous imperfect reverse disposal order, there is likely a design issue in your dependency structure that should be addressed
• Fixed bug in registerCachedFactoryParamAsync where calling getAsync would fail with null error because it was checking the wrong function parameter (sync creationFunctionParam instead of asyncCreationFunctionParam)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}