Support take_ownership parameter in helm installation (#1034) (#1092)

This is a backport of PR #1034 as merged into main (42acb4f).
SUMMARY
Adds support for the take_ownership for initial release installation operations.
ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
plugins/modules/helm.py
ADDITIONAL INFORMATION
I recently had to migrate a namespace k8s from flat manifest installation into helm a release.
I was so glad to see the take_ownership feature but realized that it work only after first installation of the release.
Seeing no reason to denied this use case i suggest this very simple changes.
To reproduce it:

Create a new namespace in any cluster.
Create a secret
Install any helm chart that deploy the same secret using take_ownership: true.

changelogs/fragments/20251224-take-ownership-helm-initialization.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Helm - Allow taking ownership of existing Kubernetes resources on the first installation of a Helm release. Previously, the ``take_ownership`` parameter was always disabled during the initial install, preventing resource adoption (https://github.com/ansible-collections/kubernetes.core/pull/1034).

plugins/modules/helm.py

@@ -246,7 +246,7 @@ options:
     version_added: 6.1.0
   take_ownership:
     description:
-      - When upgrading, Helm will ignore the check for helm annotations and take ownership of the existing resources
+      - Helm will ignore the check for helm annotations and take ownership of the existing resources
       - This feature requires helm >= 3.17.0
     type: bool
     default: False
@@ -1092,6 +1092,7 @@ def main():
                 reset_then_reuse_values=reset_then_reuse_values,
                 insecure_skip_tls_verify=insecure_skip_tls_verify,
                 plain_http=plain_http,
+                take_ownership=take_ownership,
                 skip_schema_validation=skip_schema_validation,
             )
             changed = True