Fix imageFromCacheForKey with options and context behavior, matching the async version one.

[dreampiggy]

New Pull Request Checklist

• I have read and understood the CONTRIBUTING guide

• I have read the Documentation

• I have searched for a similar pull request in the project and found none

• I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

• I have added the required tests to prove the fix/feature I am adding

• I have updated the documentation (if necessary)

• I have run the tests and they pass

• I have run the lint and it passes (pod lib lint)

This merge request fixes / refers to the following issues: ...

Pull Request Description

Support SDImageCacheDecodeFirstFrameOnly and SDImageCacheMatchAnimatedImageClass

This may be a little related to #3230 . But not solve them all.

From the design of this framework, the SDAnimatedImage custom class, should provide the top level priority.

Which means:

• If there are SDAnimatedImage custom class instance in memory cache: Always query and return it, whatever caller is UIImageView or SDAnimatedImageView
• If there are UIImage not custom class instance in memory cache: If matchesImageClass, ignore it and override with new created one SDAnimatedImage.

This can ensure we always prefer the SDAnimatedImage over UIImage, so that we do not replace same instance once by another. (If we put UIImage and SDAnimatedImage with the same level priority, this will cause huge issue)

[kinarobin]

How about add some test case ?

[dreampiggy]

How about add some test case ?

Done in the test41MatchAnimatedImageClassWorks sync version as well.