feat: Support aria2 in download widget

[hotrungnhan]

Homarr

Thank you for your contribution. Please ensure that your pull request meets the following pull request:

• Builds without warnings or errors (pnpm buid, autofix with pnpm format:fix)
• Pull request targets dev branch
• Commits follow the conventional commits guideline
• No shorthand variable names are used (eg. x, y, i or any abbrevation)

Change Logs:

• Support Aria2 in download widget.
• Download item detail:
  • Conditional render upspeed, sent and ratio to torrent's item only.
• Adjust the DownloadClientStatus interface to support the multiple download type client such aria2.

Limitations:

• Remove operation does not remove downloaded files (Aria2 RPC does not support this).
• The waiting and finished entries only listing first 1000 items.
• Can only pause downloading and leeching.
• The 'error' and completed entries can only be removed.

[deepsource-io]

Here's the code health analysis summary for commits 7a8e671..799f0cc. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[manuel-rw]

This gives me Package size exceeded the configured limit of 50 MB. Try https://github.com/homarr-labs/dashboard-icons/tree/master/png/aria2.png instead.

[Meierschlumpf]

Yeah the icon does not exist and has to be added to the dashboard-icons repository

[hotrungnhan]

Aria2 don't have any offical icon. I found in the internet the icon below, or if you find any better, please help add it to the dashboard-icons repository.

[manuel-rw]

I dislike that the category has brackets in it's name. Just a suggestion: multiProtocolDownloadClient?
@Meierschlumpf / @SeDemal WDYT?

[SeDemal]

From Aria2's main page: "It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink"
Since it supports more than http(s), and this client is the only one using all the different kinds, I suggest to just call it "miscellaneous" or something like that. All in all though, it actually boils down to the type of exchange which is one way or both ways, so http is of the same type as usenet downloads.

[hotrungnhan]

updated to use "miscellaneous"

[manuel-rw]

Why an empty file?

[SeDemal]

I'll need to spend some more time later on for a proper review.
Few things to note though:

• Properly check all the tests (pnpm -> fomrat:fix, lint, typecheck)
• Make the integration fit the current template as much as possible (I'm unsure if it's relevant here, just a reminder)
• If you're going to make your own client interpretation of the dependency, then why not get rid of it? It seems to me that a http RPC function should be fairly easy here from what I see in the docs. (nzbGet uses RPC as well, if you want a template)
• Use the proper fetch function, we use "fetchWithTrustedCertificatesAsync" because of certificates.

[hotrungnhan]

@SeDemal @manuel-rw @Meierschlumpf finished. can you help review again ?

is there existing way to disable the action button base on download item state ?