deps:chore - update elixir Docker tag to v1.19

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
elixir	final	minor	1.13-alpine -> 1.19-alpine

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

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

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[snykbotzup]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gitbotzup]

Overall Summary

This PR updates the Elixir base image used in the Dockerfile for the Elixir deployment service, upgrading from version 1.13-alpine to 1.19-alpine. This change is intended to leverage the latest features, improvements, and security patches available in Elixir 1.19.

---

Changed Files

• internal/services/formatters/elixir/deployments/Dockerfile
  • Change:
    • The base image was updated from elixir:1.13-alpine to elixir:1.19-alpine.
    • This upgrades the Elixir version used in the container from 1.13 to 1.19.

---

Security Advice & Points of Attention

• Positive Impact:
  • Upgrading to a newer base image generally enhances security by including the latest patches and fixes.
• Points of Attention:
  • Ensure that all dependencies and application code are compatible with Elixir 1.19.
  • Review for any breaking changes in Elixir between versions 1.13 and 1.19 that could affect application behavior or introduce vulnerabilities.
  • Test the application thoroughly in the updated environment before deploying to production.
    This is an AI-generated summary, which may be innacurate.
    This aims only to assist human reviewers, and does not replace code reviews in any way.
    Use responsibly and please submit any feedback to this form.