Route burst limit

[dirkhh]

Working with this for a couple of weeks we noticed two issues:

• the batches became to big, especially when users zoomed out at an aggregator site and suddenly thousands of routes were requested
• the user experience wasn't great with the five and then ten second waits This patch series limits each individual route API call to a maximum of 100 callsigns and in return allows those calls once every second. This reduces the burst load on the route API server and improves the user experience. The code has been tested on a production server :) Thanks to Katia for the idea and the testing.

[dirkhh]

Pinging @wiedehopf ... any chance this could get merged. Completely invisible to anyone not enabling the routes. But potentially painful for poor @katlol 's server. And she has too much integrity to just limit the requests on her end while users of the upstream might still send her huge requests due to the choices that I made when implementing this the first time. So I feel a little bad about this. I'll buy you a virtual beer on the discord of your choice?

[dirkhh]

It's three really tiny, painfully simple and obvious changes. With detailed commit messages. An open source maintainer's dream, really. 😇🤣