fix(eventhubs): stop authorization refresh on close

[Johnathan W (j7nw4r)]

Summary

Event Hubs ProducerClient close cycles retain authorization refresh task references and can cause sustained heap growth.

Motivation

The owned authorization refresh task keeps connection and authorizer references alive during connection teardown. This prevents producer lifecycle memory from being released promptly and matches the reported growth of about 4.8 KB per cycle.

Changes

Stops the owned authorization refresh task before RecoverableConnection teardown. Close aborts the refresh task and awaits its cancellation, so task-held references are released before close returns.

Replaces OnceLock<SpawnedTask> with a mutex-backed state machine. This removes the unsafe Send and Sync implementations.

Adds a deterministic regression test for the owned authorization refresh task and documents the fix in the 0.15.0 changelog.

Test plan

• cargo fmt -p azure_messaging_eventhubs -- --check passed.
• cargo clippy -p azure_messaging_eventhubs --all-features --all-targets -- -D warnings passed.
• cargo test -p azure_messaging_eventhubs --all-features passed. Tests configured for live service access remained skipped.
• The focused deterministic regression and git diff --check passed.

Closes #4595

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
3 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Stops Event Hubs authorization refresh tasks during connection closure to prevent retained producer lifecycle memory.

Changes:

• Cancels refresh tasks before connection teardown.
• Adds deterministic refresh-task cleanup coverage.
• Adds a live heap-growth regression test.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/common/authorizer.rs	Adds refresh-task cancellation and test configuration.
src/common/recoverable/connection.rs	Stops refresh during close and adds regression coverage.
tests/eventhubs_producer_memory.rs	Adds lifecycle heap-trend testing.

Suppressed comments (2)

sdk/eventhubs/azure_messaging_eventhubs/tests/eventhubs_producer_memory.rs:70

• A missing Event Hub name also reports this regression test as passed without running any lifecycle. Preserve the fallback name if needed, but propagate failure when neither variable is configured.

    let eventhub = match env::var("EVENT_HUB_NAME") {
        Ok(eventhub) if !eventhub.is_empty() => eventhub,
        _ => match env::var("EVENTHUB_NAME") {
            Ok(eventhub) if !eventhub.is_empty() => eventhub,
            _ => return Ok(()),

sdk/eventhubs/azure_messaging_eventhubs/tests/eventhubs_producer_memory.rs:76

• Credential construction failure silently turns the live regression into a passing no-op. Since live mode was explicitly requested, propagate this error so an unusable test environment is visible.

    let credential = match DeveloperToolsCredential::new(None) {
        Ok(credential) => credential,
        Err(_) => return Ok(()),
    };

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
3 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Sagar Patel (sagar0207)]

The core task-lifecycle fix looks sound. I found two concerns in the new live test and two documentation follow-ups.