Prevent cache from being resized

[mapogolions]

In the current implementation, additional work is done if a cache entry has already expired, but the cache is large enough to accept it. Consider the case when exceedsCapacity = false and entry.CheckExpired returns true. The cache first grows even if the entry has expired and then shrinks. It would be great in this case not to perform any manipulations regarding the cache size.
The approach I suggested would only change that expired entries won't be able to trigger cache compaction. (exceedsCapacity = true and entry.CheckExpired returns true)

[ghost]

Tagging subscribers to this area: @eerhardt, @maryamariyan, @michaelgsharp
See info in area-owners.md if you want to be subscribed.

Issue Details

---

In the current implementation, additional work is done if a cache entry has already expired, but the cache is large enough to accept it. (e.g. exceedsCapacity = false, entry.CheckExpired returns true)
The cache first grows even if the entry has expired and then shrinks. It would be great in this case not to perform any manipulations regarding the cache size.
The only thing that will change is that expired entries will not be able to trigger cache compaction. (e.g. exceedsCapacity = true and entry.CheckExpired returns true)

Author:	mapogolions
Assignees:	-
Labels:	area-Extensions-Caching, community-contribution
Milestone:	-

[dnfadmin]

All CLA requirements met.

[eerhardt]

I think this looks good. Thanks for the suggestion.

@Tratcher @adamsitnik - any concerns on this change?

[Tratcher]

Adding an expired entry should be a rare case, but the change seems fine.