Query Riot Games match-v5 API for match history and implement correct rate limit handling

Steps

1. Obtain a production API key from the Riot Developer Portal by submitting a project application; note that development keys have stricter rate limits and expire periodically.
2. Resolve the correct regional routing value for match-v5 (americas, asia, europe, sea) based on the player's platform (e.g., NA1 and BR1 route to americas); use this as the base URL host.
3. Call the match-v5 matchlist endpoint with a PUUID and optional filters (queue type, count, start index) to retrieve an array of match IDs.
4. Fetch individual match details by calling the match-v5 match endpoint with each match ID; cache responses aggressively since historical match data is immutable.
5. Implement a rate limit handler that reads the X-Rate-Limit-Count and X-Rate-Limit-Type response headers to track consumption; on a 429 response, read Retry-After and wait the specified duration before retrying.
6. Separate API calls into per-method and per-service buckets as Riot enforces both; exceed either and you receive a 429 even if the other bucket has capacity.