chore(deps): bump get_it from 7.2.0 to 7.6.0

[dependabot[bot]]

Bumps get_it from 7.2.0 to 7.6.0.

Changelog

Sourced from get_it's changelog.

[7.6.0] - 09.05.2023

• merged PR by lacopiroty fluttercommunity/get_it#297 which now allows to access objects inside GetIt by runtime type too like

    getIt.registerSingleton(TestClass());
final instance1 = getIt.get(type: TestClass);
expect(instance1 is TestClass, true);

• fix for fluttercommunity/get_it#299
• fix for fluttercommunity/get_it#300

[7.5.0] - 07.05.2023

• new function dropScope(scopeName) which allows to remove and dispose any named scope even if it's not the top one. Great PR by @​olexale fluttercommunity/get_it#292 which fixes sort of race conditions if you create scopes just for the life time of a widget.

[7.4.1]

• PR from @​dzziwny which fixed an edge case with LazySingletons fluttercommunity/get_it#284
• Changed an assertion in case that an object is not registered to an Exception that also will throw in real time so that you get meaningful errors based on fluttercommunity/get_it#312

[7.4.0]

• registerSingleton now returns the passed instance as a return value thanks to the PR by @​Rexios80 fluttercommunity/get_it#242
• In some cases GetIt will print error messages to the debug output. Now this won't happen anymore in release mode and can be completely disabled by setting GetIt.noDebugOutput=true following the PR from @​James1345

[7.3.0]

New features:

• popScopeTil got a new optional inclusive parameter so you can now decide if scope with the passed name should be popped too or only the ones above
• PR by @​jtdLab that adds to reset a LazySingleton by providing an existing instance
• Fix for an internal state error by @​ioantsaf
• Fix for a rare edge case if you manually signalReady
• Many PRs with improvements to spelling and grammar of readme, source documentation and even one assert message by @​selcukguvel @​isinghmitesh @​UsamaKarim @​nilsreichardt and Os-Prog @​Ae-Mc

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)