fix: check ownership before delete in upgrade/rollback/install (#32218) - #32793

What this PR does / why we need it:

Fixes #32218.

The delete phase of Update (pkg/kube/client.go) is annotation-blind: a resource present in the original release but absent from the target is deleted without consulting meta.helm.sh/release-name. When a resource has been adopted by another release via --take-ownership, the source release still deletes it on its next upgrade/rollback, corrupting the adopter's state.

The uninstall path already guards against this via verifyOwnershipBeforeDelete (#31584). This PR extends the same principle to the shared update() delete loop, which is reached by upgrade, rollback, and install.

Changes:

• Add opt-in ClientUpdateOptionOwnership(releaseName) to pkg/kube/client.go. When set, the delete loop reads the live resource's meta.helm.sh/release-name annotation and skips deletion when it belongs to a different release. Resources owned by the operating release, or carrying no annotation, are deleted as before. When releaseName is empty the safeguard is disabled and behavior is unchanged.
• Wire the option into all three Update call sites: upgrade.go (releasingUpgrade), rollback.go (performRollback), install.go (performInstall).
• Only release-name is checked (not namespace) to avoid edge-case false skips across namespaces. The existing private constant in pkg/action/validate.go is left untouched; pkg/kube uses its own package-private constant since it cannot import pkg/action.

Special notes for your reviewer:

This is an alternative to the stalled draft #32257 (upgrade-only). Differences:

• Covers all three Update call sites — upgrade, rollback, and install — not just upgrade. They share the same update() delete loop.
• Checks only meta.helm.sh/release-name (not release-namespace) to avoid edge-case false skips for cluster-scoped or cross-namespace resources.
• Single-param ClientUpdateOptionOwnership(releaseName) option.

The three action call sites always pass the release name, so the safeguard is always active in practice. Keeping it an explicit option preserves the pkg/kube API contract (HIP-0004): Update's option list is additive, and clientUpdateOptions.releaseName defaults to empty (disabled), so any direct caller of pkg/kube.Client.Update sees no behavior change.

A true non-destructive transfer (adopt-before-delete, no delete/recreate) is a larger enhancement and is out of scope for this fix. This PR targets the correctness goal in #32218: a release must not delete a resource owned by another release.

If applicable:

• this PR contains user facing changes (the docs needed label should be applied if so)
• this PR contains unit tests
• this PR has been tested for backwards compatibility

User-facing change: helm upgrade/rollback/install no longer deletes a resource that has been adopted by another release (via --take-ownership), and logs skipping delete of resource not owned by this release when skipping. No docs update needed — the existing --take-ownership documentation already describes the intended behavior ("Subsequent upgrades and uninstalls then treat those objects as part of the release"); this fix makes the actual behavior match that description for the source release.