Fix Docker Compose config and enhance taxonomy seeding logic

[jfrench9]

Summary

This PR addresses issues with the Docker Compose configuration and improves the taxonomy seeding logic to be more robust and reliable. The changes span infrastructure configuration and application-level seed data handling.

Key Accomplishments

Docker Compose Configuration

• Refactored compose.yaml to correct service configuration issues, ensuring containers are properly orchestrated and dependencies are resolved correctly.

Taxonomy Seeding Enhancements

• Significantly expanded the taxonomy seeding logic in robosystems/config/taxonomy/seed.py with approximately 50+ lines of new/improved code.
• Enhanced seed data handling to be more resilient, likely addressing edge cases where seeding would fail or produce incorrect results (consistent with the extensions-seed-fix branch name).
• Improved the seeding process to better handle extension-related taxonomy entries, ensuring data integrity during initial setup or migrations.

Breaking Changes

• Docker Compose changes: Existing local development environments may need to be recreated (docker compose down && docker compose up) to pick up the updated service configuration.
• No application-level breaking changes are expected, as the seeding logic changes are additive and improve existing behavior.

Testing Notes

• Verify that the Docker Compose stack starts cleanly with no service errors or dependency issues.
• Run the taxonomy seeding process from a clean state and confirm all expected taxonomy entries (including extensions) are correctly populated.
• Test idempotency: running the seed process multiple times should not create duplicate entries or cause errors.
• Validate that existing environments with pre-seeded data are not adversely affected by the updated seeding logic.

Infrastructure Considerations

• Teams using the Docker Compose setup for local development or CI/CD should pull and rebuild their environments after merging this change.
• The seeding logic changes may affect initial deployment workflows — ensure that any automated provisioning pipelines account for the updated seed behavior.
• Database state should be reviewed in staging/preview environments to confirm the seed fix resolves the originally reported issue with extensions.

---

🤖 Generated with Claude Code

Branch Info:

• Source: bugfix/extensions-seed-fix
• Target: main
• Type: bugfix

Co-Authored-By: Claude noreply@anthropic.com