Glide Options api mutates cache keys when passing a false option

Glide Options api mutates cache keys when passing a false option, which can be expected behavior. One might expect a "false" option is the same as a null option. This could result in unexpected cache misses, causing black flashes if one Glide request has option(false) and the other doesn't have the option set.

Start by tracing how Glide Options values are incorporated into cache keys; the issue does not name a file or test. Reproduce requests using option(false) and with the option unset, then verify that equivalent requests produce the same cache key and avoid unexpected cache misses.

Written by the indexing model from the issue text.