fix(cypress-schematic): suffix template files so they are not ignored

[ZachJW34]

User facing changelog

Fix cypress schematic files that were not being included in the published npm package

NOTE: Not applicable to Cypress changelog

Additional details

The folder structure for the schematic template files was recently updated but the .npmignore pattern was not, causing all of the .ts files to not be included in the published package. I opted to rename all of the .ts files to use the .template suffix, since they can contain invalid syntax and shouldn't be typechecked

Steps to test

With latest published package:

1. Create a new angular cli application with ng new my-app (might need to npm i -g @angular/cli)
2. cd my-app and run ng add @cypress/schematic
3. Follow prompts (no CT testing), and check the cypress folder, it will be missing e2e/spec.cy.ts and support/**
4. Look in node_modules/@cypress/schematic/src/schematics/ng-add/files-core, it is missing the relevant files

With local (my branch)

1. In Cypress repo: cd npm/cypress-schematic && npm pack
2. Inside new Angular app, run npm i @cypress/schematic@file:<absolute-path-to-tgz>cypress-schematic-0.0.0-development.tgz
3. Revert changes made in angular app and run ng add @cypress/schematic
4. Verify files are scaffolded correctly, check in node_modules for properly included files

How has the user experience changed?

Before:

After:

PR Tasks

• [na] Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

39662 • 0 • 3348 • 0 • 0

---

Run details

Project	cypress
Status	Passed
Commit	dc8305c
Started	Aug 31, 2022 2:41 PM
Ended	Aug 31, 2022 2:56 PM
Duration	14:53 💡
OS	Linux Debian - 11.3
Browser	Multiple

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[admah]

LGTM

[mike-plummer]

Creates file as specified, but I want to confirm expected behavior - accepting the defaults for ng add @cypress/schematic I end up with a project with E2E and CT enabled, and a single empty scaffolded e2e spec but no component spec. Feels kind of odd for something component-testing specific, but I could be over-thinking it

[ZachJW34]

@mike-plummer could be another bug, I believe the behavior for CT should be that it reads all of your component files and generates specs for each component it finds, will verify.

Edit: The defaults will give you all the scaffolding, but there is another option --addCtSpecs that must be specified in order for it to generate component tests. It's not bound to the prompts so it will default to false, not sure if that's intentional or not, @admah can verify here.

[mike-plummer]

Approving since this change fixes the intended issue