Add education demo seed and EduProject metadata

[Oluwajuwon-O]

Description

This PR addresses the database bootstrap and demo data enhancements described in the technical documentation:

Lack of Domain-Agnostic Demonstration

Historically, DOT only included a single demo project (ScanProject1) which was tightly coupled to healthcare terminology and data structures. This made it difficult to demonstrate DOT's capabilities as a generic, domain-agnostic data quality framework.

Resolution

• Education Schema Creation: Added db/dot/5-education_demo_data.sql to initialize a new education schema in the source database and populate it with synthetic tables (students, courses, enrollments, excel_grades).
• EduProject Metadata: Added db/dot/6-eduproject_metadata.sql to register the new EduProject in the DOT metadata tables. This script configures a suite of data quality tests against the new education entities.
• Validation of Multi-Tenant Architecture: This new project serves as a live demonstration of the multi-project schema isolation and domain-neutral duplicate detection features introduced in previous PRs. It proves DOT can simultaneously manage healthcare and education pipelines on the same database connection without collisions.
  Note: This PR depends on Isolate target schemas by source schema #125 and Incremental append loads with ID-based overlap deletion #126.

In the Technical Documentation, this supports the EduProject / education-schema examples in Sections 2.2 and 3.2 (bootstrap/demo data context in Section 9).

In the Technical Documentation, this is addressed in Sections 9.

Asana Task

Deployment Readiness*

Testing

Describe or check:

• Created or updated unit, feature, and/or integration tests
• Typical manual testing in the local env browser, dev pipeline, etc.

Deployment Notes

Describe or check:

• No special deployment steps required

Rollback Plan

Describe or check:

• Standard revert is sufficient (git revert)

Reviewer Guidance / Questions*

Screenshots / Testing Evidence*

SOC 2 Change Management Checklist

• None of the below are true in this code
• New roles/permissions are introduced without review and approval by the product manager
• Hardcoded credentials, secrets, or API keys are present in this code
• Secrets are being managed outside of the approved secrets management process (e.g., GitHub Secrets, environment variables)
• PII or sensitive data handling is introduced or changed without being reviewed against our data classification policy
• Sensitive data is written to logs
• Input validation and sanitization is missing
• An unnecessary attack surface has been introduced (e.g., unused endpoints, open ports, debug modes left enabled)
• Common vulnerabilities have been introduced in the code (inc. any dependencies added or updated)
• No review for common vulnerabilities has been conducted
• Not tested in a non-production environment
• Breaking changes to existing APIs or integrations with downstream consumers being notified
• Performance impact has not been considered or acceptable
• Appropriate audit logging is missing for any security-relevant actions introduced by this change
• Log entries contain sensitive or PII data
• All existing tests do not pass locally (./vendor/bin/pest)

Provide justification if you are submitting a PR with any boxes checked other than the first.

---

Reminder for Reviewers: By approving this PR you are confirming that you have reviewed the code for correctness, security, and compliance with our engineering and SOC 2 standards. Do not approve PRs where SOC 2 checklist items are checked without documented justification.

*Optional

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1217270637676993