🎯 Add unified shared types across databases and OpenAPI sources

[oyvindberg]

🚀 Summary

This PR introduces unified shared types that align TypeDefinitions across multiple data sources!

✨ Features

• 🏷️ Add SourceKind ADT to distinguish Database vs OpenAPI sources in type alignment
• 📍 Add ApiFieldKind to track model properties vs API parameters
• 📝 Generate shared types with documentation showing all aligned sources
• 🔗 Support TypeDefinitions matching across PostgreSQL, MariaDB, and OpenAPI
• 🎛️ Add fieldTypeOverrides for explicit field→type mappings in OpenAPI
• 🗺️ Include detailed location paths (e.g., Customer.firstName, /customers.isActive)

📋 Example Output

/** Shared type `IsActive` aligned across sources:
  *   - postgres (PostgreSQL): purchasing.vendor.activeflag, humanresources.employee.currentflag
  *   - mariadb (MariaDB): warehouses.is_active, payment_methods.is_active, ...
  *   - api (OpenAPI): CustomerUpdate.isActive, Customer.isActive, /customers.isActive, ...
  */
public record IsActive(@JsonValue Boolean value) { ... }

🎉 What This Enables

• 🔄 Single type definition shared across multiple databases AND OpenAPI specs
• 📊 Full traceability of where each type is used
• 🛡️ Type-safe code generation that spans your entire stack

✅ Test plan

• Verify shared types generate correctly with multi-source documentation
• Verify OpenAPI model properties and parameters are distinguished in paths
• Verify type alignment works across PostgreSQL, MariaDB, and OpenAPI

🤖 Generated with Claude Code