Bump dagger-compiler from 2.41 to 2.42

[dependabot[bot]]

Bumps dagger-compiler from 2.41 to 2.42.

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.42

What’s new in Dagger

Potentially breaking changes

As of this release, Dagger’s generated class will no longer extend the user-defined @Component annotated class (885b16dcf). This change was done to improve build times in certain scenarios by avoiding a known javac bottleneck. However, it may also be a breaking change for some users. For example

// This will fail as of Dagger version 2.42
DaggerMyComponent component = DaggerMyComponent.create();
// Do this instead:
MyComponent component = DaggerMyComponent.create();

For migration purposes, we’ve added a temporary javac flag that can be used to re-enable the legacy behavior (the flag is disabled by default).

-Adagger.generatedClassExtendsComponent=ENABLED

This flag will be removed in a future version of Dagger.

What’s new in Hilt

Bug fixes

• Fix two issues (e3d446873):
  1. matchingFallbacks being ignored work with Hilt.
  2. Hilt causing jetifier to execute twice.
• Allow Hilt view constructor to contain non-declared types. (dc76e82c0)
• Fix #3222. Generated fragment code previously would cause a Lint issue around LayoutInflater.from(). (850fc8474)
• Fix #3329 where modules in a package with non-standard capitalization could cause an error in the Hilt Gradle Plugin. (029fe5702 and 329915f5f)

Commits

• 46fc050 2.42 release
• c3f1944 Update kotlin-metadata-jvm to 4.0 which support reading metadata from upcomin...
• b60b8e5 Remove usages of .java(), toJavac(), and toXProcessing() which were nee...
• e793595 Internal Changes.
• d14a3d6 Manually pass in application instance when creating EarlySingletonComponent.
• b0aa9f1 Replace javac implementation of XProcessingEnv#isAssignable() with XProcessin...
• dfab36d Improve the error message for conflicting entry points.
• 0dfbcaa [Refactor] Move CompositeBindingGraphValidator into bindinggraphvalidation pa...
• 1a01575 Fix O(N^2) performance issue when determining declaration order.
• 75a79c0 Update the XProcessing jar
• 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 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)

[runningcode]

@dependabot rebase

[dependabot[bot]]

Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.