Don't reuse scratch textures when texsub image banned for FBO textures
Don't reuse scratch textures when texsub image banned for FBO textures

If writePixels uses a scratch surface it will likely bind it to a FBO.
If this workaround is in play that texture then becomes "poisoned" as
a temp surface for a future writePixels(). However, our caching
mechanism will still find it and we'll incur an extra recursion in
writePixels to allocate a new texture that has never been bound to a
FBO. This pattern can repeat itself with increasing recursion depth
until the cache budget has been reached and we start purging the
"poisoned" textures.

Disallowing reuse of scratch textures avoids this issue.

Bug: skia:11204
Change-Id: I8002a673900a9a34e889c92e816781d4b7f84688
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/388696
Reviewed-by: Robert Phillips <95e8ac5504948c7bf91b22c16a8dbb7ae7c66bfd@google.com>
Commit-Queue: Brian Salomon <61fabaaf0876044aeedfd8e351e485c028d69e7b@google.com>

google/skia,aosp-mirror/platform_external_skia,google/skia,aosp-mirror/platform_external_skia,aosp-mirror/platform_external_skia,aosp-mirror/platform_external_skia,google/skia,google/skia,aosp-mirror/platform_external_skia,google/skia,aosp-mirror/platform_external_skia,aosp-mirror/platform_external_skia,aosp-mirror/platform_external_skia,google/skia,aosp-mirror/platform_external_skia,aosp-mirror/platform_external_skia,google/skia,google/skia,google/skia,google/skia