Reset mark position after skipping past the mark limit. Any later res…

…et will throw instead of leaving the stream in a bad/undefined state.

Previously, this would cause us to lose track of the bytes that were skipped. For PNGs, ExifInterface skips past the entire data block, which for some files can exceed the buffer limit. We would return back to the buffer location, decode the image partially and then try to load more from the wrapped stream - which would lead to a quick EOF

This is similar to what fillbuf does when we push past the mark limit.

PiperOrigin-RevId: 349315836

library/src/main/java/com/bumptech/glide/load/resource/bitmap/RecyclableBufferedInputStream.java

@@ -393,7 +393,14 @@ public synchronized long skip(long byteCount) throws IOException {
       pos = count;
       return read;
     }
-    return read + localIn.skip(byteCount - read);
+
+    // We can't skip over the remaining bytes without exceeding the mark limit so there will be no
+    // way to reset to a proper position in the stream.
+    long skipped = localIn.skip(byteCount - read);
+    if (skipped > 0) {
+      markpos = -1;
+    }
+    return read + skipped;
   }
 
   /**