Retry Failed Requests to 'v1/api/torrents/requestdl' endpoint

Often with larger torrents with many contained files, I am finding that the download(s) are often incomplete when choosing to select/copy all links to feed to a download manager like JDownloader. Upon further investigation I noticed that, often enough, several requests to the 'https://api.torbox.app/v1/api/torrents/requestdl?' API endpoint are failing with HTTP status 500, and are not retried. Since a request is generated for every individual file, this results in the incomplete capture of download links when using this feature. I have a feeling this also affects users simply choosing to download via their browser, as the actual download links are not generated in this case.

I'm currently mitigating this on my end via a semi-convoluted process - I wrote a script that converts the JSON response data previously fetched in the browser from the endpoint `https://db.torbox.app/rest/v1/torrents?select=*` into a CSV format. I then return a list of all filenames with their extensions from the download directory, which is used to filter the list of all files in the torrent (in the CSV), by matching the filenames against the 'short_name' JSON parameter, and return only the missing files. Lastly, I use a script to fetch the download links for these missing files/failed requests from the `https://api.torbox.app/v1/api/torrents/requestdl?` endpoint using a valid token, and have added retry logic on failure from my end at this point. Happy to share all of these with the developers of the site if further context is required to understand - and yes, I am being respectful so as to not bombard your endpoint with a ton of concurrent requests at once :)

Additionally - a bug report - I also am often finding that, when copying these links using the button, the clipboard often contains a blank 'block' of text space, with no characters, or simply contains 'null'.