Cache prices provider token info per address

[iamacook]

Description

We are caching prices provider responses based on query parameters. These parameters may include multipl token addresses, of varying order, e.g. {url}?token=a,b,c vs. {url}?token=b,a,c. As such, we are caching inconsistently.

We should be caching token info per address, checking whether they exist first before requesting those missing. This will, in turn, reduce the number of requests to our prices provider.

Reproduction steps

1. Request prices of tokens in a certain order.
2. Adjust order and request again.

Observe cache miss on second request.

Expected behavior

Cache hit should occur for given example.

Additional information

No response