Trothling of UI components

[tomLandry]

Limit number of possible slider and zoom event to one every 250 ms. Goal is to set a limit in the number of requests a user can send to the server.

[Zvax]

@tomLandry Can you help me circumvent the scope? By "possible slider and zoom event" I assume you mean everywhere in the site? Can you list the different screens / widgets that interact with zoom and change where that happens and how to navigate to them?

Having a specific list of places where I need to envision the throttling would help me accomplish this in a reasonable timeframe and as I am not overly familiar with the site, I would be glad to have some assistance here.

[tomLandry]

So basically, same type of implementation you did for the time slider throthling. This one is done, we could get a tighter implementation but it felt fine.

The other things we need to restrict is the zoom on the maps, but mostly from the mouse scroll. I'm easily able to completely swamp the server. So limiting to one zoom in/out every 300ms or so. Hopefully it's not completely managed by Leaflet, or you can override the event handler.

[Zvax]

While discussing with Tom:

The only URL to be addressed is https://climatedata.ca/explore/variable. We only address the mouse scroll event on the map accessed from there.

[tomLandry]

One completed, the modifications (code that can be patched on the browser-side) should be submitted to @jordanharding and @habitatseven for validation. They'll give it a go to confirm the portal still "feels good", reactive and quick, after throthling. Once approved, @ldperron will pull this changes as well as other changes into prod.