feat(container)!: Update image app-template to v3

[renovate]

This PR contains the following updates:

Package	Update	Change
app-template	major	2.6.0 -> 3.6.0

---

Configuration

📅 Schedule: Branch creation - "on saturday" (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 was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

The git diff provided shows updates to various Helm chart versions from 2.6.0 to 3.0.2 across different Kubernetes workloads ranging from addons like a Discord notifier and System Upgrade Controller, to monitoring tools like Gatus and Unifi-poller, as well as several networking tools including Cloudflared and an Echo server. These changes do not inherently introduce direct security issues from the information given; however, there are considerations and recommendations to ensure the security and reliability of these updates:

1. Ensure Compatibility and Security of New Versions: Before updating to a new version of a chart or software, it's crucial to review the release notes and security advisories for that version. This ensures that the update does not introduce any known vulnerabilities and is compatible with your current setup.

   Fix/Suggestion:

   - Make sure to review the release notes and security advisories for version `3.0.2` of each chart being updated. This is to ensure that no new vulnerabilities are introduced and that there are no breaking changes or incompatibilities with your current setup.

2. Helm Repository Trust: The changes reference a Helm repository named bjw-s. Ensure that this repository is a trusted source for your Helm charts. Using charts from untrusted sources can potentially introduce malicious code into your cluster.

   Fix/Suggestion:

   - Verify that the Helm repository (`bjw-s`) is a trusted and secure source for your Helm charts. Consider using only well-known and vetted repositories for your Helm chart needs.

3. Dependency Updates: When updating a Helm chart, it also updates its dependencies. It's important to ensure that these dependencies do not introduce vulnerabilities.

   Fix/Suggestion:

   - Alongside reviewing the main chart's release notes and version changes, make sure to review and verify any updated dependencies for security issues or incompatibilities.

4. Automated Security Scanning: If not already in place, integrating automated security scanning and policy enforcement tools can help detect security concerns in Helm charts or Kubernetes configurations early in the development process.

   Fix/Suggestion:

   - Integrate a tool for automated security scanning of Helm charts and Kubernetes configurations, such as Checkov, Kubescape, or Snyk, to detect and resolve potential security issues before deployment.

The above suggestions are preemptive measures to ensure that updates do not compromise the security or integrity of the applications and infrastructure. Given the limited context in the git diff (e.g., it doesn't include detailed configuration changes, environment-specific settings, or the exact contents of the new chart versions), no direct security issues can be identified explicitly from the changes themselves. However, the considerations and mitigations provided are best practices for securely managing updates and dependencies in a Kubernetes environment.