(feature request) Internal torrent client for external torrent files

If there was an internal torrent client, people could make links or source references (``, ``) to torrent files on the site (e.g. a video, zip file, etc), clicking the links would start seeding the file and streaming the gathered pieces to the browser, and a torrent manager could be another internal page. Such links may look like `http://127.0.0.1:43110/torrent/1GAKtBpSxrZk6VKPS6iythg3VbQEwgS7yU/content/cat.webm.torrent`. Cancelling the download from the browser or closing the content tab would not stop the torrent, it would still continue from the torrent manager, where it can be cancelled, paused, deleted, or re-served to the browser from the cache (also could be done by following the same torrent link).

Start by mapping the proposed /torrent/... content URL and the internal torrent manager described in the issue. Determine the project entry points for serving torrent content and managing downloads, then define the browser, caching, seeding, pause, cancel, delete, and re-serving behavior that would constitute a complete implementation.

由索引模型根据 Issue 内容生成。