chore(deps): update dependency community.sops to v1.6.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
community.sops	galaxy-collection	minor	1.4.1 -> 1.6.2

---

Release Notes

ansible-collections/community.sops

v1.6.2

Compare Source

======

Release Summary

Maintenance release.

Bugfixes

• install role - make sure that the pkg_mgr fact is definitely available when installing on localhost. This can improve error messages in some cases (https://github.com/ansible-collections/community.sops/issues/145, https://github.com/ansible-collections/community.sops/pull/146).

v1.6.1

Compare Source

======

Release Summary

Maintenance release.

Bugfixes

• action plugin helper - fix handling of deprecations for ansible-core 2.14.2 (https://github.com/ansible-collections/community.sops/pull/136).
• various plugins - remove unnecessary imports (https://github.com/ansible-collections/community.sops/pull/133).

v1.6.0

Compare Source

======

Release Summary

Feature release improving the installation role.

Minor Changes

• install role - add sops_github_latest_detection option that allows to configure which method to use for detecting the latest release on GitHub. By default (auto) first tries to retrieve a list of recent releases using the API, and if that fails due to rate limiting, tries to obtain the latest GitHub release from a semi-documented URL (https://github.com/ansible-collections/community.sops/pull/133).
• install role - add sops_github_token option to allow passing a GitHub token. This can for example be used to avoid rate limits when using the role in GitHub Actions (https://github.com/ansible-collections/community.sops/pull/132).
• install role - implement another method to determine the latest release on GitHub than using the GitHub API, which can make installation fail due to rate-limiting (https://github.com/ansible-collections/community.sops/pull/131).

v1.5.0

Compare Source

======

Release Summary

Feature release.

Minor Changes

• Automatically install GNU Privacy Guard (GPG) in execution environments. To install Mozilla sops a manual step needs to be added to the EE definition, see the collection's documentation for details (https://github.com/ansible-collections/community.sops/pull/98).

New Playbooks

• community.sops.install - Installs sops and GNU Privacy Guard on all remote hosts
• community.sops.install_localhost - Installs sops and GNU Privacy Guard on localhost

New Roles

• community.sops.install - Install Mozilla sops

---

Configuration

📅 Schedule: Branch creation - "on sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
❌ ANSIBLE	ansible-lint	yes		1	15.43s
✅ COPYPASTE	jscpd	yes		no	1.32s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	1.06s
✅ YAML	prettier	1		0	0.49s
✅ YAML	yamllint	1		0	0.19s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by