Suppress execution context from token renewal

[jviau]

Suppress execution context from the background token renewal operations. The renewal uses the logger, and so we will capture whatever current log scope is present, leaking that scope into this background thread. This is both a small memory leak and potential object disposed failure (the log scope or its contents may be disposed at any point).

Issue describing the changes in this PR

resolves #issue_for_this_pr

Pull request checklist

• [x] My changes do not require documentation changes
  • [ ] Otherwise: Documentation PR is ready to merge and referenced in pending_docs.md
• [ ] My changes should not be added to the release notes for the next release
  • [x] Otherwise: I've added my notes to release_notes.md
• [x] My changes do not need to be backported to a previous version
  • [ ] Otherwise: Backport tracked by issue/PR #issue_or_pr
• [x] I have added all required tests (Unit tests, E2E tests)
• [x] My changes do not require any extra work to be leveraged by OutOfProc SDKs
  • [ ] Otherwise: That work is being tracked here: #issue_or_pr_in_each_sdk
• [x] My changes do not change the version of the WebJobs.Extensions.DurableTask package
  • [ ] Otherwise: major or minor version updates are reflected in /src/Worker.Extensions.DurableTask/AssemblyInfo.cs
• [x] My changes do not add EventIds to our EventSource logs
  • [ ] Otherwise: Ensure the EventIds are within the supported range in our existing Windows infrastructure. You may validate this with a deployed app's telemetry. You may also extend the range by completing a PR such as this one.
• [x] My changes should be added to v3.x branch.
  • [ ] Otherwise: This change only applies to Durable Functions v2.x and will not be merged to branch v3.x.

[jviau]

I wonder if this will address https://github.com/Azure/azure-functions-durable-extension/issues/2771?