build(deps): bump dagger from 2.57.2 to 2.58 in /02_arch/android

[dependabot]

Bumps dagger from 2.57.2 to 2.58.
Updates com.google.dagger:hilt-android from 2.57.2 to 2.58

Release notes

Sourced from com.google.dagger:hilt-android's releases.

Dagger 2.58

Note: The next Dagger release will require AGP 9 when using the HiltGradlePlugin. (e92e3f392)

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• a8b6ee3 2.58 release
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• 8aabfe1 Internal changes
• e574adb Optimize Dagger Provisioning: Reuse Existing Framework Instances
• d41e836 Enable useBindingGraphFix=true by default.
• 54af480 Refactor ComponentRequirement to compute NullPolicy at creation time.
• e47643b Optimize Dagger Provisioning: Reuse Existing Framework Instances
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-compiler from 2.57.2 to 2.58

Release notes

Sourced from com.google.dagger:hilt-compiler's releases.

Dagger 2.58

Note: The next Dagger release will require AGP 9 when using the HiltGradlePlugin. (e92e3f392)

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• a8b6ee3 2.58 release
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• 8aabfe1 Internal changes
• e574adb Optimize Dagger Provisioning: Reuse Existing Framework Instances
• d41e836 Enable useBindingGraphFix=true by default.
• 54af480 Refactor ComponentRequirement to compute NullPolicy at creation time.
• e47643b Optimize Dagger Provisioning: Reuse Existing Framework Instances
• Additional commits viewable in compare view

Updates com.google.dagger.hilt.android from 2.57.2 to 2.58

Release notes

Sourced from com.google.dagger.hilt.android's releases.

Dagger 2.58

Note: The next Dagger release will require AGP 9 when using the HiltGradlePlugin. (e92e3f392)

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• a8b6ee3 2.58 release
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• 8aabfe1 Internal changes
• e574adb Optimize Dagger Provisioning: Reuse Existing Framework Instances
• d41e836 Enable useBindingGraphFix=true by default.
• 54af480 Refactor ComponentRequirement to compute NullPolicy at creation time.
• e47643b Optimize Dagger Provisioning: Reuse Existing Framework Instances
• Additional commits viewable 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)