Fix Komga and Mihon extension integration

[mon5termatt]

Summary

Fixes Mihon extension sources (especially Komga) failing after library restore: extension settings were invisible, browse/details requests broke on /api/v1/...\ URLs, and Cloudflare/interactive network errors were not surfaced with a resolve action in snackbars.

Changes

• Extension settings UI — \SourceSettingsExt\ falls back to reflection when a direct \ConfigurableSource\ cast fails across extension vs app classloaders (Komga Address/Username/Password).
• Komga API URLs — \MihonDataConverters\ preserves absolute /api/v1/...\ URLs and resolves relative Komga paths against the configured server base URL.
• Network error handling — unwrap nested Mihon/OkHttp exceptions so Cloudflare and interactive-action errors propagate correctly; snackbar resolve actions walk the cause chain and work from fragments without an injected resolver.

Notes

• Cursor: Used to help write and iterate on this code; I reviewed the diff before opening the PR.
• Testing: Leaving this as a draft while I run it on a Samsung Galaxy S24 Ultra for a few days (Komga restore, browse/details, Cloudflare sources, etc.) before marking ready for review.

Test plan

• Restore a backup containing Komga favourites on S24 Ultra
• Install Komga extension, open source settings, configure server address/credentials
• Browse Komga library and open manga details without /api/v...\ scheme errors
• Cloudflare-protected sources show a snackbar with a Continue/resolve action
• Daily-use smoke test over several days

Out of scope

A separate Mihon backup converter CLI lives on my fork branch \mihon-convert\ and is intentionally not included in this PR.

[mon5termatt]

I want to test this for a few days and make sure it can read all my personal files and potentially add komga as an actual source not just mihon ported.

[LandWarderer2772]

I shall test on my machines as well

[LandWarderer2772]

Btw, join the Discord if you want to talk about development and stuff :)