Shaded Dagger dependency, fixes #342

[uKL]

Before:

Task :rxandroidble:countReleaseDexMethods 
Total methods in rxandroidble-release.aar: 2234 
Total fields in rxandroidble-release.aar:  1072 
Total classes in rxandroidble-release.aar:  513 
AAR size 374kB

After:

Task :rxandroidble:countReleaseDexMethods 
Total methods in rxandroidble-release.aar: 2180 
Total fields in rxandroidble-release.aar:  976 
Total classes in rxandroidble-release.aar:  510 
AAR size 363kB

Additionally, there is a JAR with 41kB with the shaded Dagger containing 187 methods.

[dariuszseweryn]

💯 All good.
I would like to see the difference in the library size and method count after this change.

[dariuszseweryn]

I am thinking if this should land in 1.5.0 or 1.4.4... Thoughts?
On one hand the API does not change at all. On the other the we change the dependencies and someone could have used the transitive dagger dependency?

[uKL]

Having used a transitive dependency is an antipattern anyways. The same was with the rxandroid when we removed it.

In case of the dagger, there is a small chance that someone is using it this way due to the compiler dependency. It has to be added directly.

[dariuszseweryn]

Antipattern or not-still it can be something that breaks builds.
If we agree that it is just a bugfix then we should go with 1.4.4 but I think we already have some additional changes towards 1.5.0 there

[uKL]

Just to be safe we can go forward to 1.5.0 (we have changes related to operation timeout)

[dariuszseweryn]

I am just thinking whether we should temporarily revert operation timeout changes, release 1.4.4 with the shaded dagger and then go back to 1.5.0 with the operation timeout changes applied again

[uKL]

I'm gonna need them soon anyway so we can go with 1.5.0.