Torrent endpoints for a single torrent are using the infohash instead of the ID

[josecelano]

API Issue: torrust/torrust-index#115
API PR: torrust/torrust-index#140

Some endpoints containing information about a single torrent have changed. Now, we use the info hash instead of the torrent ID automatically generated by the database. The endpoints are:

• GET /torrent/download/{id} -> GET /torrent/download/{infohash}
• GET /torrent/{id} -> GET /torrent/{infohash}
• PUT /torrent/{id} -> PUT /torrent/{infohash}
• DELETE /torrent/{id} -> DELETE /torrent/{infohash}

@WarmBeer @da2ce7

[josecelano]

For example, the endpoint to upload a new torrent: torrust/torrust-index#146. The new response included the info-hash:

pub struct NewTorrentResponseData {
    pub torrent_id: TorrentId,
    pub info_hash: String,
}

See https://github.com/torrust/torrust-index-backend/blob/develop/src/web/api/v1/contexts/torrent/responses.rs#LL11C1-L14C2

We need to change the type for that response here to fix an issue in the frontend repo:

torrust/torrust-index-gui#97

We can change all the endpoints to mirror the current state of the API. That means we could need to change other endpoints too. Review all of them.

[josecelano]

Done in this commit 4f10e04.