Associate tagged keys with entries so replacements are not evicted

[profet23]

Associate tagged keys with entries so replacements are not evicted

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

MemoryOutputCacheStore will now only remove tags from the associated eviction, rather than all tags associated with the key.

Description

A previous PR (#43728) fixed a memory leak by removing tags upon eviction from the MemoryOutputCacheStore.

That fix created a bug where if an entry is replaced rather than evicted via timeout, the tags associated with the replacement would erroneously be deleted and the new entry would have no tags.

This PR associates each tag with a specific entry. When the PostEvictionCallback is run, only the associated tags with that specific eviction will be removed.

I based this on release/8.0 branch, I assume it can be merged into release/8.0, release/9.0, and main.

Fixes #61524

[dotnet-policy-service]

Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at.

[martincostello]

I based this on release/8.0 branch, I assume it can be merged into release/8.0, release/9.0, and main.

As a starting point this should target main. If it meets the servicing bar, then backporting it to other branches can be done by the team post-merge.

[profet23]

I based this on release/8.0 branch, I assume it can be merged into release/8.0, release/9.0, and main.

As a starting point this should target main. If it meets the servicing bar, then backporting it to other branches can be done by the team post-merge.

Done.

[gfoidl]

Code changes LGTM.

[dotnet-policy-service]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.

[profet23]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 61529 in repo dotnet/aspnetcore

[profet23]

Anything more I need to do to get a review and keep this PR from going stale?