[client] Extend API client features for platform demo

[frgfm]

Following up on pyronear/pyro-platform#19, the following features need to be added to the client:

• Read all devices within the scope of the user
• Read the sites
• Read the list of device IDs of a given site at a given time (which ongoing on the API-side in [installations] Adding a route to list of devices on a site at a given time #49)
• Read the alerts (while we don't have a webhook)
• Download the frame (media) linked to an alert

Considering the scopes of several routes are going to change (more restricted) with #45, this is all the more important since, if they are able to use GET on some routes without authentication, this might not be true in the future!

[Akilditu]

Thanks for this issue @frgfm !

Adding to the needs the ability to access the medias (frames) that triggered the alerts as we will display them in the platform (let's say at least on frame per alert for 1.0)

[florianriche]

I am starting a PR to add the functions to the Client; stop me if somebody already started working on it !

[florianriche]

For the last point, shall the API returns a real media or just the bucket_key to retrieve the image (from Carnot computing buckets)?

To me, it seems it would be a big load to put on the API to retrieve the images.

Or are we saying it is the API Client's job to retrieve those medias? In that case it's fine by me.

[Akilditu]

For the last point, shall the API returns a real media or just the bucket_key to retrieve the image (from Carnot computing buckets)?

To me, it seems it would be a big load to put on the API to retrieve the images.

Or are we saying it is the API Client's job to retrieve those medias? In that case it's fine by me.

That's a good point.

Maybe easier for demo that API handles this