Handle different Station Storages for different information

[eliemichel]

For instance, the position and the name of a station won't change, so it can be saved locally, but the bikes and stands available change always and so have a different timeout.

This also means that the timeout should be different depending on the function.

And we should considere lazy loading focused on close stations. Nevertheless, we should also run some benchmark as it is faster to perform one big request than a lot of small ones.

Meanwhile, I disable local storage.

(Note that as for now, no update is made while the application remains open.)

Milestones:

• Monitor and handle timeouts while the application is still running
• Use different timeouts for availability and permanent information
• Restore LocalStationStorage
• Perform two ways loading: When the LocalStationStorage is ready, add markers with loading icon instead of availability counts and when AuthorityStationStorage is ready, update those availabilities.
• Study the pros and cons of proximity loading only for the AuthorityStationStorage.