[F01] Establish repository technical setup

[Maleesha101]

Related Issue

Closes #2

Summary

Establishes the F01 technical foundation after the documentation foundation in PR #21.

Included

• Editor and Git repository conventions
• Pull request template
• CODEOWNERS baseline
• Feature, bug, and security issue templates
• CI repository validation workflow
• Local environment template
• Minimal PostgreSQL Docker Compose dependency
• Make-based developer validation commands
• Technical setup documentation

Intentionally excluded

• Application services
• Authentication/authorization implementation
• FHIR APIs
• WSO2/Siddhi
• Kubernetes
• LLM gateway
• PQC implementation

Those will be introduced with their respective feature/platform issues.

Validation

• Repository structure and required foundation files are validated by CI.
• Local Compose configuration is defined through docker-compose.yml.
• Make validation commands are provided.
• Runtime execution of the CI workflow is pending GitHub Actions execution on this PR.

Security impact

• Adds environment and private-key ignore rules.
• CI checks for accidentally tracked environment/private-key files.
• No secrets or real healthcare data are introduced.

Database impact

• Adds a local PostgreSQL development dependency only.
• No application schema or migrations are introduced.

API/FHIR impact

• None.

Documentation impact

• Adds docs/development/technical-setup.md.

Known limitations

• Application-specific test/lint/security jobs will be added when application code exists.
• CODEOWNERS currently uses the repository organization as the ownership baseline and should be refined when team ownership is finalized.

[Maleesha101]

Addressed all requested review comments in PR #24:

• Added the requested editor configuration handling in .gitignore and clarified that the project-level .editorconfig remains intentionally tracked.
• Added a UI Evidence section to the PR template requiring screenshots for UI changes and explicitly prohibiting sensitive/real healthcare data in evidence.
• Kept FHIR, identity, and other platform dependencies out of the F01 Compose baseline. Added documentation explaining that these dependencies will be introduced in their dedicated feature/platform iterations.
• Added development runtime guidance: Node.js 22 LTS and Go 1.25+, plus the current WSO2 FHIR Server compatibility baseline (FHIR R4, PostgreSQL 14–18).
• Resolved all four review threads.

The F01 scope remains intentionally minimal and reproducible; the deferred services will be added when their respective implementation issues begin.

[kavix]

LGTM! I'll add other dependencies after finalizing scope and stack