More ratelimit fixes

[amCap1712]

1. Fix ZeroDivisionError.
2. Pass auth token to relevant api calls in LB radio patch.

[github-actions]

Test Results

  4 files  ±0    4 suites  ±0   4s ⏱️ ±0s
 50 tests ±0   50 ✅ ±0  0 💤 ±0  0 ❌ ±0 
200 runs  ±0  200 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 1b9ba31. ± Comparison against base commit abd9965.

[github-actions]

Package	Line Rate	Complexity	Health
.	33%	0	❌
content_resolver	0%	0	❌
content_resolver.formats	6%	0	❌
content_resolver.model	0%	0	❌
external	39%	0	❌
listenbrainz	46%	0	❌
musicbrainz	72%	0	➖
patches	27%	0	❌
patches.lb_radio_classes	0%	0	❌
tools	20%	0	❌
.	33%	0	❌
content_resolver	0%	0	❌
content_resolver.formats	6%	0	❌
content_resolver.model	0%	0	❌
external	39%	0	❌
listenbrainz	46%	0	❌
musicbrainz	72%	0	➖
patches	27%	0	❌
patches.lb_radio_classes	0%	0	❌
tools	20%	0	❌
.	33%	0	❌
content_resolver	0%	0	❌
content_resolver.formats	6%	0	❌
content_resolver.model	0%	0	❌
external	39%	0	❌
listenbrainz	46%	0	❌
musicbrainz	72%	0	➖
patches	27%	0	❌
patches.lb_radio_classes	0%	0	❌
tools	20%	0	❌
.	33%	0	❌
content_resolver	0%	0	❌
content_resolver.formats	6%	0	❌
content_resolver.model	0%	0	❌
external	39%	0	❌
listenbrainz	46%	0	❌
musicbrainz	72%	0	➖
patches	27%	0	❌
patches.lb_radio_classes	0%	0	❌
tools	20%	0	❌
Summary	21% (4303 / 20182)	0	❌

[amCap1712]

If we merge this change, we also need to update this line in LB to pass a token to troi to make use of the better ratelimit.
https://github.com/metabrainz/listenbrainz-server/blob/e10e33bb5abb01282dea60ada70ca5564e520eee/listenbrainz/webserver/views/explore_api.py#L184

However, now I wonder whether we should do that as it would let people DDoS pretty easily? I think instead of passing a whitelisted token always there we should forward the token received in the API call to that endpoint to troi. So the higher ratelimit would only be allowed if we invoked the endpoint.

[mayhem]

If we merge this change, we also need to update this line in LB to pass a token to troi to make use of the better ratelimit. https://github.com/metabrainz/listenbrainz-server/blob/e10e33bb5abb01282dea60ada70ca5564e520eee/listenbrainz/webserver/views/explore_api.py#L184

However, now I wonder whether we should do that as it would let people DDoS pretty easily? I think instead of passing a whitelisted token always there we should forward the token received in the API call to that endpoint to troi. So the higher ratelimit would only be allowed if we invoked the endpoint.

Very good thinking, lets do that.

[mayhem]

Who could've thought that an API first toolkit could run into so many rate limitings issues? 🤷