MangaLivre: handle chapter route tokens

[atiladpribeiro]

Summary

• request the official per-chapter route token with the current reading-gate signature
• attach x-toon-route-token only to chapter page-list requests
• cache tokens using the server expiry and refresh them after a chapter 404
• refresh both the seed and route token after a 403
• bump the extension to 1.4.87

Root cause

The site now requires a short-lived token from /api/chapter-token/{mangaId}/{chapterId} for each chapter API request. The chapter endpoint deliberately returns 404 when x-toon-route-token is missing or stale.

Performance

The token is fetched once per chapter and cached until shortly before the server-provided expiry. Normal catalog, search, details, and image requests do not perform this extra call. Recovery is bounded to one retry and does not use a WebView.

Validation

• :src:pt:mangalivre:clean
• :src:pt:mangalivre:assembleDebug
• :src:pt:mangalivre:lintDebug
• live catalog, details, and chapter list against toonlivre.net
• live page-list and image rendering for chapters 129 and 128 of Mestre Espadachim Criado Pelas Estrelas
• no HTTP 403, HTTP 404, ABI error, or crash in the final runtime logs

Checklist:

• Updated versionCode
• Kept the source name, language, and ID unchanged
• Kept all added requests on toonlivre.net
• Used kotlinx.serialization
• Did not hardcode a User-Agent
• Tested the complete source-to-reader path
• This PR is AI-assisted; I reviewed the changes and validated the behavior