Add initial skeleton for Visit Summary report using ReportManager–Renderer architecture

[PawanTheGod]

Overview

This PR introduces a basic skeleton for a Visit Summary report within the patientdocuments module.

The implementation follows the existing ReportManager–Renderer architecture used in the module.

---

Changes

• Added VisitSummaryDataSetDefinition with visitUuid parameter
• Added VisitSummaryReportManager to define report structure
• Added VisitSummaryPdfRenderer to generate a minimal PDF output
• Added constants and i18n entries for the new report

---

Dependency Update

• Added OpenPDF dependency to api/pom.xml for PDF generation
• Removed redundant test-scope OpenPDF dependency from omod/pom.xml

---

Purpose

This is an initial step toward implementing a configurable Visit Summary report as discussed in GSoC 2026 ideas.

The current implementation is intentionally minimal and establishes a clean foundation for future enhancements such as:

• aggregation of clinical data (vitals, diagnoses, medications, labs)
• configurable report sections
• template-based rendering

---

Testing

• Verified successful build using mvn clean install
• Ensured compatibility with existing module structure

---

Notes

• This is a skeleton implementation (no real data aggregation yet)
• Designed for future extensibility

---

Feedback is welcome on whether this approach aligns with the expected direction.