Bump com.autonomousapps.dependency-analysis from 1.33.0 to 2.0.1

[dependabot[bot]]

Bumps com.autonomousapps.dependency-analysis from 1.33.0 to 2.0.1.

Changelog

Sourced from com.autonomousapps.dependency-analysis's changelog.

Version 2.0.1

• [Fix] consider dependency unused candidate if only capability is InferredCapability.

Version 2.0.0

• [Feat] add 'com.autonomousapps.build-health' settings plugin.
• [Feat] dependencyAnalysis configurable from settings script.
• [Feat] remove support for auto-apply flag.
• [Feat] remove restriction that DAGP must be applied to root project.
• [Feat] helpful error message when KGP or AGP are missing from build classpath.
• [Feat] check that buildHealth did something.
• [Feat] remove deprecated ignoreKtx property.
• [Feat] move PluginAdvice to the model package.
• [Feat] rename FindInlineMembersTask to FindKotlinMagicTask.
• [Feat] don't warn when AGP is using a newer patch version
• [Fix] gracefully handle 'empty' Android res file.
• [Chore] update to Gradle 8.9
• [Chore] update to AGP 8.5.2

Commits

• 443d426 Prepare for release 2.0.1.
• 1003ed0 fix: consider dependency unused candidate if only capability is InferredCapab...
• fb043fb docs: update changelog.
• 31443da Prepare next development version.
• c4de3ea Prepare for release 2.0.0.
• b45a2f3 feat: register dependencyAnalysis extension on settings script.
• deea787 docs: update changelog.
• 4352628 fix: remove flags that have been deprecated for a long time.
• 20aab08 feat: check that buildHealth did something.
• c0f71aa fix: check Gradle version at least 8.8 when applying build-health plugin.
• 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 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[bot]]

Code Coverage

Overall Project	48.45% -0.05%	🟢
Files changed	0%	🟢

Module	Coverage
Kover Gradle Plugin XML report for :plugins	9.44% -1.07%	🟢

Files

|Module|File|Coverage|| |:-|:-|:-|:-:| |Kover Gradle Plugin XML report for :plugins|[PillarboxAndroidApplicationPlugin.kt](https://github.com/SRGSSR/pillarbox-android/blob/66c84ea715b43086a6d98bc33351ae30c64f3d74/build-logic%2Fplugins%2Fsrc%2Fmain%2Fjava%2Fch%2Fsrgssr%2Fpillarbox%2Fgradle%2FPillarboxAndroidApplicationPlugin.kt)|0% **`-3.37%`**|🟢| ||[PillarboxAndroidLibraryPlugin.kt](https://github.com/SRGSSR/pillarbox-android/blob/66c84ea715b43086a6d98bc33351ae30c64f3d74/build-logic%2Fplugins%2Fsrc%2Fmain%2Fjava%2Fch%2Fsrgssr%2Fpillarbox%2Fgradle%2FPillarboxAndroidLibraryPlugin.kt)|0% **`-4.26%`**|🟢|

[MGaetan89]

@StaehliJ I've updated the PR to use the new configuration for this plugin. Now it needs to be applied on every module, not only on the root one. I've also updated the corresponding workflow step, so it always displays the analysis report.