fix: prepare server 1.7.2

[Priveetee]

Summary

• update PipePipeExtractor from f156813dd4bbebf3b4dffe541fee6c27ae1dd294 to ca3280f28f3aa0b980b63a2b2d23c362f7616620
• prepare Server version 1.7.2
• keep BiliBili extraction at the Extractor boundary instead of adding a route or frontend fallback

Production behavior

The production Server 1.7.1 image returned HTTP 422 for BV1pfto6TEwo?p=1 because the old BiliBili metadata path left watch null and the Extractor dereferenced it. The new Extractor uses the WBI metadata endpoint, validates the response, and returns playable streams for the affected video.

Deployment requirements

No database migration or configuration change is required. Recreate only typetype-server with the published 1.7.2 image digest after the Docker workflow completes.

Runtime verification

• direct production reproduction recorded HTTP 422 with the old image
• the beta image already using ca3280f returned HTTP 200 with BiliBili streams
• the exact issue URL extracted playable streams in the local network probe with the hotfix dependency
• ./gradlew test
• ./gradlew check
• ./gradlew shadowJar
• git diff --check

Rollback

Restore Server image digest sha256:c33675e2665314c0f86dca1bd75e24170e0beff2a50f1e878494b9bbf20d8438 and recreate only typetype-server.