Fixes a complicated bug due to the interaction between the cache and the @lazy(_property) decorator.
Fixes a complicated bug due to the interaction between the cache and the @lazy(_property) decorator.

It worked as follows:
1) we pull a Summoner, it get's put in the cache
2) we hit summoner.current_game, which stores the current game in the lazy property
3) we stop using the summoner and it goes out of scope
4) we access the summoner again an hour later, it gets pulled out of the cache
5) we hit summoner.current_game again, and the current game is pulled from the lazy property because the summoner in the lazy property's WeakKeyDictionary never got garbage collected since it was stored in the cache.
In this way a new current game could never be pulled unless the summoner was removed from the cache.

We just decided to make these properties not-lazy instead:
summoner.mastery_pages
summoner.rune_pages
summoner.match_history
summoner.current_match
summoner.leagues
summoner.league_positions

10se1ucgo/cassiopeia,meraki-analytics/cassiopeia,robrua/cassiopeia