chore(deps): update office integration charts

[amamus]

Description

Updates the oCIS Office example's six stale Helm dependencies while keeping the application images aligned with the current ocis_full source profile:

• Apache Tika chart 3.2.2 with its matching full 3.2.2.0 image
• RabbitMQ chart 16.0.14 with the OnlyOffice-documented 4.1.3 image
• Redis chart 22.0.7 with the OnlyOffice-documented 8.2.1 image, preserving the existing replicated topology
• Zalando PostgreSQL operator chart 1.15.1
• OnlyOffice Docs chart 6.0.0 with distributed images pinned to 9.3.1-1, corresponding to the source-tested DocumentServer 9.3.1.1 release
• Collabora Online chart 1.3.2 with the application image pinned to the source-tested 26.04.3.1.1 release

The OnlyOffice pre-install retry patch is retained and its source link now points at chart v6.0.0.

Tika 3.2.2 remains on the classic Apache repository because it is the newest official stable package there; the currently documented OCI location does not publish a stable 3.2.2 artifact. OnlyOffice chart 6.0.0 is intentional because its job templates and distributed images were released together for the 9.3.1 application family; forcing those images into chart 6.1.1 would mix them with 9.4.1-era job scripts.

Related Issue

• Related to Dependency Dashboard #433
• Source of truth: https://github.com/owncloud/ocis/tree/c62b830e932384ba42203b2ed32b10fa42a7f9a5/deployments/examples/ocis_full

Motivation and Context

The example still selected older Tika 2.x, RabbitMQ, Redis, PostgreSQL operator, OnlyOffice 8.3, and Collabora 24.04 releases. This made the Kubernetes example diverge from the maintained source profile and left it exposed to old chart APIs, images, and defects.

This PR overlaps the single-package Renovate PRs #895, #896, #899, and #935, but it covers the complete source-compatible office dependency set and the required image/value compatibility work.

There is no commit dependency on another alignment PR. PR #959 independently adds Tika to the Web-app example and should adopt the same Tika 3.2.2 chart and 3.2.2.0-full image before it merges. Its unmerged feature changes are intentionally not duplicated here.

How Has This Been Tested?

• test environment: macOS arm64; Helm 3.16.2; Helmfile 0.169.1; Kustomize 5.8.1; Kubeconform 0.6.7; KubeLinter 0.6.8
• all ten releases in the Office Helmfile passed Helmfile lint, including every updated external chart
• the complete Office stack rendered 180 resources; focused parsed assertions verified every chart/image pin, all eleven OnlyOffice workloads/jobs, service and Secret contracts, Redis master plus three replicas, PostgreSQL pooler settings, and the patched pre-install Job backoff limit of 20
• strict Kubeconform validation passed on Kubernetes 1.28, 1.29, 1.30, and 1.31: 175 valid resources, zero invalid resources, and five intentionally skipped custom-resource kinds per version
• Docker Hub metadata checks returned HTTP 200 for every pinned Tika, RabbitMQ, Redis, OnlyOffice, and Collabora image
• the core chart passed all three Helm lint profiles and its configured KubeLinter check; all ten repository deployment examples passed their CI Helmfile lint selection
• schema generation was idempotent; YAML parsing and diff checks passed

Screenshots (if appropriate):

Not applicable.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added (not applicable; configuration-only dependency update)
• Acceptance tests added (not applicable; configuration-only dependency update)
• Documentation generated (not applicable; no chart values or generated documentation changed)
• Documentation ticket raised (not applicable)
• Documentation PR created (not applicable)