[Snyk] Upgrade software.amazon.awssdk:cloudfront from 2.31.37 to 2.41.10

[akilarootcode]

Snyk has created this PR to upgrade software.amazon.awssdk:cloudfront from 2.31.37 to 2.41.10.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 167 versions ahead of your current version.

• The recommended version was released a month ago.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Updates the backend’s AWS CloudFront SDK dependency version as part of an automated Snyk dependency upgrade, to keep the project’s Maven dependencies current.

Changes:

• Bump software.amazon.awssdk:cloudfront from 2.31.37 to 2.41.10.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This bumps AWS SDK v2 cloudfront to 2.41.10 while s3 in the same POM is still pinned to 2.31.56. Mixing AWS SDK v2 module versions can cause dependency convergence conflicts and runtime linkage errors. Consider importing the AWS SDK BOM in dependencyManagement (and removing per-module versions) or at least aligning the s3 version to 2.41.10 too.