fix: resolve Glide 4.16.0 compatibility issues for image loading

- Updated MyAppGllideModule to use Registry directly instead of glide.getRegistry()
- Added isManifestParsingEnabled() override returning false to prevent manifest parsing conflicts
- These changes fix image loading failures introduced by Glide upgrade from 4.11.0 to 4.16.0

The Glide 4.16.0 version introduced breaking changes in how modules register components.
This fix ensures proper OkHttp integration with the custom HTTP client configuration.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: graycreate

app/src/main/java/me/ghui/v2er/general/MyAppGllideModule.java

@@ -24,11 +24,16 @@
 
 @GlideModule
 public class MyAppGllideModule extends AppGlideModule {
+    
+    @Override
+    public boolean isManifestParsingEnabled() {
+        return false;
+    }
 
     @Override
     public void registerComponents(Context context, Glide glide, Registry registry) {
         OkHttpUrlLoader.Factory factory = new OkHttpUrlLoader.Factory(APIService.httpClient());
-        glide.getRegistry().replace(GlideUrl.class, InputStream.class, factory);
+        registry.replace(GlideUrl.class, InputStream.class, factory);
     }
 
     @Override