increase authorized device timeout

Personne n'a encore pris cette issue.

Currently I am asked to "sign in" to authorise my device (my iMac) every 1-2 hours.
This happens regardless of whether I create a new localstack instance or not.
This is very frustrating as the interface only shows what was available before the page eg cloudwatch logs is force refreshed which then triggers a new sign in screen.

Ideally the auth mechanism for the device (in this case my iMac) should last longer than 1 hour,
a week would be ideal.
This would facilitate a much better user development experience.

To replicate this:

- Create a localstack instance
- open localstack desktop
- click on the instance
- click on "Resource browser"
- click the "log in" button
- copy the provided code and paste it into the opened web page in your browser
- hi the aythorise button in the browser.
- close the browser window.
- do some work and open a log group in cloudwatch logs
- note how many log streams ar available
- do some more work leaving the desktop app open for about 1+ hours
- do work that generates a new log stream in the group you chose previously
- go back to the desktop app and click the link to go back to cloudwatch logs in the breadcrumbs path
- select the same group you chose previously
- note that there are no new log streams with respect to your recent work
- force refresh the page (command+shift+R on my Mac)
- click the "login" button that now appears
- repeast steps to copy code, paste code and authorise device.
- Refreshing the logstream at this point may or may not work and you may need to click on the home icon and navigate all the way back through the instance and resource browser to find the log stream tou were previously viewing and see it does indeed have the log stream of the most recent work.

As you can see this is very frustrating as without doing a "force refresh" to trigger a sign in flow no new data is shown in the interface.
This also make it look like the infrastructure being developed is not working when it actually is and its the interface thats not updating.

Apologies for the long explanation ;)

I hope this can be resolved easily
cheers

Commencez par les étapes de reproduction pour le Resource browser et les CloudWatch logs de LocalStack Desktop, en vous concentrant sur le flux d’autorisation de l’appareil et le comportement d’actualisation après une heure. Le travail sera considéré comme terminé lorsque l’autorisation restera disponible pendant la période plus longue demandée et que les nouveaux flux de logs apparaîtront sans actualisation forcée ni nouvelle connexion.

Rédigé par le modèle d'indexation à partir du texte de l'issue.