Refactor ColaManga to use WebView for page loading

[Howard20181]

Replaces the previous deobfuscation and key mapping logic with a WebView-based approach for loading and decrypting manga pages. Adds a new webview-script.js asset for image extraction and communication with the app. Integrates data image interceptors and improves error handling for timeouts and script loading failures.

Closes #9286

Checklist:

• Updated extVersionCode value in build.gradle for individual extensions
• Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
• Referenced all related issues in the PR body (e.g. "Closes #xyz")
• Added the isNsfw = true flag in build.gradle when appropriate
• Have not changed source names
• Have explicitly kept the id if a source's name or language were changed
• Have tested the modifications by compiling and running the extension through Android Studio
• Have removed web_hi_res_512.png when adding a new extension

[Howard20181]

Note: debug for JavaScript part
https://gist.github.com/Howard20181/7cb220417da9451f135b9b999845d2ec

[Howard20181]

Will take a look tomorrow.

[Howard20181]

All request changes resolved.

[Howard20181]

Now the pages that have been read will be cleared, and CG will not be triggered continuously because of the large amount of memory usage.

[Howard20181]

It's hard to sync the status between the webview and the app. Before all bugs are fixed, mark it draft.

[Howard20181]

The loading failure caused by state synchronization issues has been fixed. However, there is no guarantee that the WebView will be destroyed after the chapter has been fully loaded.
In this case, the webview will not be destroyed: quickly flip back through several chapters and then flip forward through several chapters. Only the first few pages of each chapter are read. Then, read the last 5 pages of the previous chapter you stopped at. In this case, the reader only reads the first few pages and then switches to another page, while preloading also begins. It cannot be guaranteed that all chapters of the webview created each time will be filled into the pagesMap.
The number of WebViews is limited to a maximum of five, and they will be forcibly recycled after 30 minutes. This is not a major issue.