build(deps): bump com.google.dagger:dagger-compiler from 2.47 to 2.51.1

[dependabot]

Bumps com.google.dagger:dagger-compiler from 2.47 to 2.51.1.

Release notes

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

Dagger 2.51.1

New Dagger Features

• Added BindingGraphPlugin#onProcessingRoundBegin for pre-processing initialization. (2a6a0b461)

Dagger bug fixes

Fixed #4181: Associate Dagger Android output with the generated Component, so that incremental builds with Ksp won’t fail. Fixed #4254: Support using scoped @LazyClassKey map bindings. Fixed #4262: Support referencing an array of annotations in a map key annotation.

Dagger 2.51

New Dagger Features

• Added a @LazyClassKey annotation that supports using class names as a map key. Unlike the existing @ClassKey, the map generated by @LazyClassKey won’t eagerly load all of the classes for the keys. This can be useful in situations or environments where classloading can be expensive, such as on Android. For more information, see https://dagger.dev/dev-guide/multibindings

Potential breaking changes

• Protected fields using @Inject are now banned in Kotlin classes. This is because Kotlin protected fields are not accessible by code in the same package, unlike Java. This has been working up to this point because Dagger generates Java code, but that is unintentional and would break if Dagger switched to generate Kotlin code.(408431a3b)

New Hilt Features

• Fixed #3197: Used the new @LazyClassKey Dagger feature to remove the keep rule for @HiltViewModel class names. This allows obfuscation of @HiltViewModel annotated ViewModel class names with R8. (0786d0af5)
• Added @SkipTestInjection which can be used for skipping test injection in Hilt Android tests, which may be useful if building separate custom test infrastructure to inject the test class from another Hilt component. (c40811e71)

Dagger bug fixes

• Improve Dagger MissingBinding error messages to give more information and be more consistent. (c8722386a)
• Fixed #4201: Suppress warning for casting in Dagger generated code. (813ffced8)
• Fixed #4203: Removes @Deprecated annotation causing warnings (3cbc94ad3)
• Fixed #4199: Support member injections from type aliased superclass (662d82359)
• Complete Ksp support for Dagger Android: Added a Ksp Processor for Dagger Android ProguardProcessor that was previously missed. The ProguardProcessor is a Dagger Android implementation detail that makes sure the AndroidInjector works correctly when shrinking tools obfuscate @ContributesAndroidInjector annotated injector class names. (e71de27a1)

Dagger 2.50

Dagger

Potential breaking changes

• Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
• Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)

Bug fixes

• Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)

Dagger 2.49

Dagger

New features:

• Fixed #4044: Add support for KSP with dagger.android (832717767).

Potential breaking changes:

• Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract @Provides/@Binds methods (ed47d4b88).

... (truncated)

Commits

• 394cf25 2.51.1 release
• 8689679 Update xprocessing.jar for Dagger.
• 2a6a0b4 Reset processingEnv for BindingGraphPlugins for each round.
• fc2363d Associate Dagger Android output with generated Component.
• 29d9a8e Make LazyClassKeyMap accept both MapFactory and MapProviderFactory
• c213e36 Fix bug in AnnotationExpression.
• e6c2ac8 Delete obsolete documentation
• e8e1ce6 Fix diagnostic kind in InjectValidator.
• 3fa9a8a Migrate from soon-to-be-deprecated propagateIfPossible to equivalent `throw...
• 922ff50 reduce number of times resolving parameter types in an extreme case.
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Superseded by #1960.