Fixes #2318.

Fixes #2322.

It's easier to just call a method than it is to set a component specific
option and it looks like disabling hardware configs is going to be
relatively common.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=167035799

Ensure that restarted request use the updated model when failed/canceled as it can contains data to help the request to succeed. (#2293)

Otherwise when our extension methods mutate the RequestOptions we pass 
them, the mutations create a new RequestOptions object that’s dropped
at the end of the extension method, which causes any options applied in
the extension method to be ignored. Cloning first matches the behavior
of other RequestOptions methods and ensures that the RequestOptions 
object passed into the extension method is mutable. 

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=166499393

This allows us to apply scale transformations if we decode from a video but
still use the hardware config if we decode from an image. Unfortunately it
won't work for custom transformations that only scale. We'd probably have to
extend the Transformation API to let transformations indicate that they only
scale and I'm not sure that that's common enough to be useful.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=166406311

*** Reason for rollback ***

b/64987553

*** Original change description ***

Choose whether or not to use HARDWARE bitmaps based on transformations in Glide.

Previously we were checking only against the requested and actual size
of the image as a heuristic to see if we thought a transformation would
be applied. That doesn't work well for certain types of transformations
that don't necessarily change the size of the image but do change its
shape (rounded corners, circle crop etc).

Now we're explicitly checking to see if a transformation will be applied
to the load and I...

***

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=166268954

Previously we were checking only against the requested and actual size
of the image as a heuristic to see if we thought a transformation would
be applied. That doesn't work well for certain types of transformations
that don't necessarily change the size of the image but do change its
shape (rounded corners, circle crop etc).

Now we're explicitly checking to see if a transformation will be applied
to the load and I've removed the heuristic. This should catch cases like
CircleCrop and also allow us to use hardware bitmaps when doing scaling
entirely within Downsampler.

In addition, we're now not applying transformations to Bitmaps for scale
only transformations that can be done with DownsampleStrategies alone.
This is a change in behavior, but since the Transformations were no-ops
previously, it should be low risk.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=166253525

If the RequestOptions object has auto clone enabled, apply() will leave the original object unmodified and return a new mutated copy. Right now RequestManage is ignoring the new mutated copy and retaining the old unmodified object which causes Glide to ignore the applied options.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=166084541

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165989169

Previously we'd use RGB_565 in a couple of cases.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165976352

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165778077

*** Reason for rollback ***

b/64845448

*** Original change description ***

Support HARDWARE Bitmaps in Android O+ in Glide.

From adb shell dumpsys meminfo com.google.android.apps.photos on a 2016
Pixel on OPM1.170816.001:

Before:
App Summary
                       Pss(KB)
                        ------
           Java Heap:    20360
         Native Heap:    66032
                Code:    93336
               Stack:     1192
            Graphics:    85892
       Private Other:     8956
              System:    19944

               TOTAL:   295712       TOTAL SWAP PSS...

***

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165772656

apply may return new object if autoClone() is enabled on a 
RequestOptions object that is passed into the builder via setDefaultRequestOptions.

Work toward #2193.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165717599

From adb shell dumpsys meminfo com.google.android.apps.photos on a 2016
Pixel on OPM1.170816.001:

Before:
App Summary
                       Pss(KB)
                        ------
           Java Heap:    20360
         Native Heap:    66032
                Code:    93336
               Stack:     1192
            Graphics:    85892
       Private Other:     8956
              System:    19944

               TOTAL:   295712       TOTAL SWAP PSS:       82

After:
App Summary
                       Pss(KB)
                        ------
           Java Heap:    20456
         Native Heap:    39756
                Code:    93384
               Stack:     1220
            Graphics:    81460
       Private Other:     9024
              System:    11662

               TOTAL:   256962       TOTAL SWAP PSS:       81

These numbers aren't super solid. Some extra invalidations can dump more
Bitmaps into our Bitmap pool which will make it look like the steady
state memory usage is increasing even though the maximum amount remains
the same. That said, I see between a 33% and 50% improvement in native
heap usage after this change. This was tested by flinging back and forth
in the All grid in Photos.

This change is limited to HARDWARE Bitmap support. We ought to also be
able to reduce the bitmap pool size in O+ now that we only care about
re-using Bitmaps for very small images or while generating thumbnails
for the first time.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165717498

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165653043

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165650311

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=165002367

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=164752684

Fixes #2266.

Running requests are left to complete to avoid cancelling and restarting
expensive operations (network or I/O). Completed requests are asked to
begin again, but short cut the normal request pipeline and redeliver the previously loaded resource to ensure that Targets and RequestListeners 
are notified as expected. Failed, cancelled, paused etc requests (all 
other states) are simply restarted.

This avoids writing partial data if the buffer is not at position 0 when the method is called. This fixes a bug where using DiskCacheStrategy.ALL
or DiskCacheStrategy.RESOURCE with GifDrawables would result in partial
and invalid gif files being written to Glide’s disk cache.

Fixes #2237.

* Added phone lookup for local URIs and updated sample to use it. Improved license handling in sample

* Checkstyle fixes

Fixing issues reported by checkstyle on travis

* Code formatting

Updated formatting after code review. Removed line of code that was commented-out. Added comment for permission request.

Fixes #2240.