WebAPI: add new method setTags to upsert tags on torrents

[zze0s]

This is another optimization for torrent management on large scale instances with the goal to minimize the amount of required API calls. Ref #22128

This new function and endpoint torrents/setTags does an upsert to replace the torrent tags and handles the removal and add internally, instead of doing multiple calls to add and remove tags on torrents from the client.

I experimented with adding handling for HTTP PUT since that would be more correct than a POST for this, but did not include those changes.

Should the API version be updated in this PR as well or is that done before a new version is released?

• Tested locally and works as expected

[Chocobo1]

I would suggest you move this code to TorrentsController::setTagsAction() instead.
And revert all changes to base/bittorrent.

[zze0s]

Thanks for reviewing! If that's desired over this solution sure! Is the reasoning to not add additional functions to the core that can be done in the caller with existing methods?

[Chocobo1]

Is the reasoning to not add additional functions to the core that can be done in the caller with existing methods?

Yes. And it seems this operation is exclusive to webapi.

[zze0s]

Got it! This made it a much smaller and simpler change 👍

Should API_VERSION in

qBittorrent/src/webui/webapplication.h

Line 57 in 76e1040

inline const Utils::Version<3, 2> API_VERSION {2, 11, 3};

Be bumped in this PR to 2.12.0 or is that done separately? Should probably have incremented that with my previous pr, unless it's done just once before a new version is tagged.