separated template repo CI workflow from generated project CI workflow

[nickhart]

Summary

Reduced complexity of CI workflows by separating out the template repo's e2e CI which tests the generation of a project and its preflight.sh steps (lint, format, built, test). Generate a separate CI workflow from a template for generated projects.

Changes

• added new CI template for generated projects
• simplified the template project's CI
• updated dev-sync.sh to not copy the template project's CI
• updated setup.sh to create the generated project's CI workflow from the template

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Configuration change
• ♻️ Code refactoring
• 🧪 Test improvements
• 🔒 Security update

Testing

• Unit tests pass (./scripts/test.sh)
• UI tests pass (./scripts/test.sh --ui)
• Manual testing completed
• Code builds successfully (./scripts/build.sh)
• Linting passes (./scripts/lint.sh)
• Formatting is correct (./scripts/format.sh)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published