Extend MemoryCacheOptions with TrackLinkedCacheEntries

[adamsitnik]

fixes #45592

[ghost]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[ghost]

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

Issue Details

---

fixes #45592

Author:	adamsitnik
Assignees:	-
Labels:	area-Extensions-Caching, needs-breaking-change-doc-created
Milestone:	7.0.0

[eerhardt]

    public async Task OnceExpiredIsSetToTrueItRemainsTrue()

Any reason why this test wasn't turned into a Theory?

---

Refers to: src/libraries/Microsoft.Extensions.Caching.Memory/tests/CacheEntryScopeExpirationTests.cs:513 in 4684c51. [](commit_id = 4684c51, deletion_comment = False)

[adamsitnik]

Any reason why this test wasn't turned into a Theory?

There is just one entry being created in this test (no dependencies to other linked entries) and it just verifies whether setting entry as expired is thread-safe (not related to tracking)

[eerhardt]

LGTM. Thanks!

[eerhardt]

Failures are unrelated. Timing out due to dotnet/core-eng#14346

[EgorBo]

arm64 improvements: dotnet/perf-autofiling-issues#1537

[adamsitnik]

To be honest I've not merged it because I wanted to check if something in ASP.NET repo is going to get broken with this change. It has been a month since it was merged and nobody started screaming. I guess it just proves that it was good idea to introduce the breaking change and disable the tracking by default.

[sebastienros]

@adamsitnik someone finally screamed

[ericstj]

@adamsitnik were you planning to create a breaking change document for this?

[maryamariyan]

I just added dotnet/docs#31739

[adamsitnik]

I just added dotnet/docs#31739

@maryamariyan big thanks for doing that!