Maxi Rosson

Add support to deprecate dependencies and report if we are using it on the code. To deprecate a lib, just add a @Deprecated annotation to the dependency constant

https://mrhaki.blogspot.com/2016/09/gradle-goodness-use-command-line.html https://mrhaki.blogspot.com/2018/05/gradle-goodness-command-line-options.html https://docs.gradle.org/current/userguide/command_line_interface.html https://docs.gradle.org/current/userguide/custom_tasks.html#sec:declaring_and_using_command_line_options

Configuration sample: `excludes = ["com.groupid1:artifactA:1.2.3"]`

For android artifacts, on `listDependenciesToUpgrade` task and the PR generated by the `upgradeDependencies` task, display all the manifest permissions diff against the previous version.

On `listDependenciesToUpgrade` task and the PR generated by the `upgradeDependencies` task, display the artifacts size diff against the previous version.

In the `validateDependencies` task, check If the code reference a class from a transitive dependency and it is not explicitly declared on `dependenciesClassNames`. This plugin can be useful: https://github.com/plnice/can-i-drop-jetifier

In the `validateDependencies` task. If you define a dependency A with v1.0.0 and a transitive dependency also defines it but with v2.0.0, we should warn about it https://docs.google.com/drawings/d/1_NAK02QrckJ1y-SVMrb740XSZ6UsKzbuFqYQmRfrRnw/edit?ts=5da12819

Sometimes we want to exclude a major upgrade (because we need to migrate the app to adapt it), but we still want minor or patch upgrades Note: this requires adding...

Sometimes the libraries change their group and/or artifact id. We should notify about that.