Bump get_it from 7.6.0 to 7.6.4

[dependabot]

Bumps get_it from 7.6.0 to 7.6.4.

Changelog

Sourced from get_it's changelog.

[7.6.4] -04.09.2023 fixed the throwing of a StateError that was previously thrown as String [7.6.3] -04.09.2023 push new version because pub didn't list this one [7.6.2] -31.08.2023 fix linter error [7.6.1] - 31.08.2023 version bump of dependencies and updates readme [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

[7.2.0]

• fix for fluttercommunity/get_it#210
• Parameters of factories are no longer needed to be casted because they are nullable
• downgraded the dependency on async to 2.6 again
• you couldn't push two Scopes without a name

[7.1.4]

• fixed bug with manual synchronization of SingletonsWithDependencies fluttercommunity/get_it#196

... (truncated)

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if either of these two conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

Other

🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.

[github-actions]

This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.

[dependabot]

Looks like get_it is up-to-date now, so this is no longer needed.