chore: prepare qconnection 0.5.2 release

[eareimu]

Summary

Prepare a staged member-crate release for qconnection 0.5.2 only, and mirror the gmutils tag workflow behavior by creating a GitHub Release automatically from tag-triggered CI.

This PR keeps the repository/workspace release version at 0.5.1 and only bumps:

• qconnection package version to 0.5.2
• workspace dependency requirement for local qconnection to 0.5.2

It also updates Publish crates.io so v* tag runs create a GitHub Release after the publish step succeeds. Release notes come from the annotated tag body when present, with authentication/provenance appended like gmutils.

Release plan

• Release surface: crates.io package qconnection only
• Release type: incremental member-crate release
• Planned tag after merge: v0.5.2-qconnection
• Publication path: tag-triggered Publish crates.io workflow
• GitHub Release path: same tag-triggered workflow, after crate publish succeeds
• Registry state: all selected workflow crates at 0.5.1 are already published; qconnection 0.5.2 is the only missing initialized version
• Dependency wait conditions: none found

Traversal is intentionally excluded from the release gate for this PR per release-operator direction.

Tag notes draft

• Release qconnection 0.5.2 with connection close/termination cleanup fixes.
• Track final closed state and route close events through the broker/termination cleanup path.
• Retain connections while closing so PTO-driven cleanup can finish.
• Keep silent close paths silent and cover close handoff cleanup.
• Update publish workflow selection so staged tags publish only crates with missing initialized versions.
• Create a GitHub Release automatically on v* tag-triggered publish runs.

Verification

• cargo +nightly fmt --all -- --check
• cargo publish --dry-run --locked --allow-dirty -p qconnection
• cargo test --workspace --all-features --all-targets -- --test-threads=1
• cargo +nightly clippy --all-targets --all-features -- -Dwarnings
• cargo build --workspace
• cargo publish --dry-run --locked -p qconnection
• registry-selection check: publish_selection=qconnection
• ruby -e 'require "yaml"; YAML.load_file(".github/workflows/publish-crates.yml"); puts "yaml ok"'
• git diff --check

[codecov]

Codecov Report

❌ Patch coverage is 97.29730% with 5 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
qconnection/src/lib.rs	94.44%	3 Missing ⚠️
qconnection/src/state.rs	93.75%	2 Missing ⚠️

Files with missing lines	Coverage Δ
qconnection/src/builder.rs	97.32% <100.00%> (+0.25%)	⬆️
qconnection/src/events.rs	94.64% <100.00%> (-0.23%)	⬇️
qconnection/src/termination.rs	91.60% <100.00%> (+11.82%)	⬆️
qconnection/src/state.rs	92.85% <93.75%> (-0.67%)	⬇️
qconnection/src/lib.rs	68.43% <94.44%> (-3.98%)	⬇️

... and 24 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.