fix(pikpak): align Worker protocol with OpenList

[chius-me]

Summary

• switch PikPak authentication and drive requests to the Worker-compatible .mypikpak.net endpoints and client ID used by OpenList-Worker
• remove the browser-oriented device/CAPTCHA request state and headers, cleaning legacy provider state during reauthorization
• align list and download metadata parameters with the reference driver while retaining ilist's encrypted token storage and proxied original downloads
• expose only stable upstream diagnostics and update setup guidance/tests

Migration

Existing PikPak mounts should be reauthorized after deployment because tokens issued for the previous client protocol may not refresh with the new client ID. Use a newly rotated password or a compatible refresh token.

Validation

• npm run check
• 49 Worker test files / 463 tests
• 16 UI test files / 142 tests
• 2 script test files / 12 tests

Refs #4

Reference: https://github.com/OpenListTeam/OpenList-Worker