Chore(deps): Bump hiltAndroid from 2.52 to 2.54

[dependabot]

Bumps hiltAndroid from 2.52 to 2.54.
Updates com.google.dagger:hilt-android-compiler from 2.52 to 2.54

Release notes

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

Dagger 2.54

Bug fixes

• Fixed #4303: Upgrade Hilt Gradle Plugin to support KSP2 configuration. (76b581999)
• Fixed #4544: Removes private from InstanceHolder field to avoid unnecessary accessor method. (07d8f883f)
• Fixed #4533: Fixes path separator for Windows when creating LazyClassKey proguard file. (efa421a3f)

Notable changes

• In preparation for jakarta support, Dagger’s generated factories now include a create() method that uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() method is also kept for compatibility, but it will be removed in a future release. When that happens, libraries built with the newer version of Dagger may break downstream users of @Component that are built with an older version of Dagger. (d60729d20)

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

Scopes are now banned on @Binds that delegate to production implementations.

New: Scoping an @Binds method that delegates to an @Produces implementation is not allowed. The scope was ignored anyway because production bindings are implicitly scoped. (03b237ff2)

Suggested fix: Remove the scope annotation (since the scope was ignored, this should not be a functional change).

@Module
interface MyModule {
-    @ProductionScoped
     @Binds fun bindToProductionImpl(impl: FooImpl): Foo
</tr></table> 

... (truncated)

Commits

• bf4b96e 2.54 release
• 76b5819 Update Hilt Gradle Plugin KSP configuration to support KSP2
• 013a9a4 Add Nullmarking to Components
• 07d8f88 Remove private from generated Factory's INSTANCE field.
• efa421a Update Dagger's XProcessing jars.
• fe9a2f9 Update Dagger to use Android SDK 34.
• 5e50a92 Internal changes
• d60729d Change Dagger-genenerated factories to have an additional create method that ...
• 6ee6092 Migrate FrameworkType and FrameworkField to XPoet.
• 972c8d3 Fix warnings about instantiating new boxed primitives.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android from 2.52 to 2.54

Release notes

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

Dagger 2.54

Bug fixes

• Fixed #4303: Upgrade Hilt Gradle Plugin to support KSP2 configuration. (76b581999)
• Fixed #4544: Removes private from InstanceHolder field to avoid unnecessary accessor method. (07d8f883f)
• Fixed #4533: Fixes path separator for Windows when creating LazyClassKey proguard file. (efa421a3f)

Notable changes

• In preparation for jakarta support, Dagger’s generated factories now include a create() method that uses dagger.internal.Provider rather than javax.inject.Provider. For now, the javax.inject.Provider create() method is also kept for compatibility, but it will be removed in a future release. When that happens, libraries built with the newer version of Dagger may break downstream users of @Component that are built with an older version of Dagger. (d60729d20)

Dagger 2.53.1

Bug fixes

• Fixes #4525: Update kotlin-jvm-metadata to 2.0.21 to remove dependency on Beta version. (84d3aa5f1)
• Fixes #4526: Add the originating element in LazyMapKeyProxyGenerator. (5fd8ec1a3)

Dagger 2.53

Potentially breaking changes:

@Binds methods now requires explicit nullability

New: @Binds methods must explicitly declare nullability (previously we tried to infer it from the parameter). This change aligns the nullability behavior of @Binds with how nullability is treated elsewhere in Dagger by requiring it to be explict at the request and declaration sites. (4941926c5)

Suggested fix: If you get a failure due to this change, add the proper nullability to your @Binds method/parameter. For example:

@Module
interface MyModule {
-    @Binds fun bindToNullableImpl(impl: FooImpl): Foo
+    @Binds fun bindToNullableImpl(impl: FooImpl?): Foo?
}

Scopes are now banned on @Binds that delegate to production implementations.

New: Scoping an @Binds method that delegates to an @Produces implementation is not allowed. The scope was ignored anyway because production bindings are implicitly scoped. (03b237ff2)

Suggested fix: Remove the scope annotation (since the scope was ignored, this should not be a functional change).

@Module
interface MyModule {
-    @ProductionScoped
     @Binds fun bindToProductionImpl(impl: FooImpl): Foo
</tr></table> 

... (truncated)

Commits

• bf4b96e 2.54 release
• 76b5819 Update Hilt Gradle Plugin KSP configuration to support KSP2
• 013a9a4 Add Nullmarking to Components
• 07d8f88 Remove private from generated Factory's INSTANCE field.
• efa421a Update Dagger's XProcessing jars.
• fe9a2f9 Update Dagger to use Android SDK 34.
• 5e50a92 Internal changes
• d60729d Change Dagger-genenerated factories to have an additional create method that ...
• 6ee6092 Migrate FrameworkType and FrameworkField to XPoet.
• 972c8d3 Fix warnings about instantiating new boxed primitives.
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.