chore(deps): update docker.elastic.co/kibana/kibana docker tag to v8.16.1

[renovate]

This PR contains the following updates:

Package	Update	Change
docker.elastic.co/kibana/kibana (source)	minor	8.14.3 -> 8.16.1

---

Release Notes

elastic/kibana (docker.elastic.co/kibana/kibana)

v8.16.0: Kibana 8.16.0

Compare Source

Downloads: https://elastic.co/downloads/kibana
Release notes: https://www.elastic.co/guide/en/kibana/8.16/release-notes-8.16.0.html

v8.15.4: Kibana 8.15.4

Compare Source

Downloads: https://elastic.co/downloads/kibana
Release notes: https://www.elastic.co/guide/en/kibana/8.15/release-notes-8.15.4.html

v8.15.3: Kibana 8.15.3

Compare Source

Downloads: https://elastic.co/downloads/kibana
Release notes: https://www.elastic.co/guide/en/kibana/8.15/release-notes-8.15.3.html

v8.15.2: Kibana 8.15.2

Compare Source

Downloads: https://elastic.co/downloads/kibana
Release notes: https://www.elastic.co/guide/en/kibana/8.15/release-notes-8.15.2.html

v8.15.1: Kibana 8.15.1

Compare Source

Downloads: https://elastic.co/downloads/kibana
Release notes: https://www.elastic.co/guide/en/kibana/8.15/release-notes-8.15.1.html

v8.15.0: Kibana 8.15.0

Compare Source

Downloads: https://elastic.co/downloads/kibana
Release notes: https://www.elastic.co/guide/en/kibana/8.15/release-notes-8.15.0.html

---

Configuration

📅 Schedule: Branch creation - "after 5pm every weekday,before 3am every weekday,every weekend" in timezone Europe/London, 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.

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".