Introduce FamilyDataService and USPTOService to enrich OPS family data and harden parsing

[srdco]

Motivation

• Provide a resilient, configurable way to retrieve patent family members using EPO OPS as primary source and USPTO ODP to enrich or fall back for US records.
• Avoid runtime errors when OPS payloads omit optional arrays like inventor/applicant by making parsing defensive.
• Make configuration for USPTO ODP endpoints available and avoid brittle usage of Pdo\Mysql symbol in environments where it may not be defined.

Description

• Added app/Services/FamilyDataService.php which orchestrates OPSService and newly added USPTOService and returns either OPS families or USPTO-enriched data via getFamilyMembers.
• Added app/Services/USPTOService.php which queries configurable USPTO ODP endpoints, normalizes payloads into title, applicants, inventors, and procedure, and exposes enrichFamilyMembers and getApplicationData helpers.
• Hardened app/Services/OPSService.php parsing to safely handle missing nodes and to filter/normalize applicant and inventor lists before assigning them to the family array.
• Updated app/Http/Controllers/MatterController.php to inject and use FamilyDataService (replacing direct OPSService calls) and added empty-array guards before iterating applicants/inventors when creating matters.
• Added USPTO configuration options to config/services.php under a uspto key and made config/database.php handle the Pdo\Mysql symbol more defensively.

Testing

• Ran the project's automated test suite with phpunit and php artisan test, and the existing tests completed successfully.
• No new automated tests were added for USPTO/OPS integration in this change set.

---

Codex Task