64: Fix new:component web templates with tests

[roblafeve]

Description

It was discovered that the web templates had the incorrect contents (it ended up being the mobile template contents). This revealed the fact that we need tests to prove correctness. Beyond that, the new:component script has branching that should be validated as well. Tests have been added for these variants.

🔗 Reference

Relevant links (e.g. issue, design, etc.)

#64

📋 Acceptance Criteria

Checked off by PR Assignees

The following snapshots accurately reflect the intended contents of each file in each scenario (and tests pass):

• tests/app-mobile/snapshots/new:component.test.ts.snap
• tests/app-web/snapshots/new:component.test.ts.snap

🔎 Reviewer Checklist

Checked off by PR Reviewers

• Merge destination is correct
• Code is correct as understood and conforms to quality standards
• Tests have been added where appropriate (unit, visual, end-to-end)
• Acceptance Criteria have been met

---

Roles & Responsibilities

👨‍💻 Assignee

• Initiator of this PR (be sure to set in GitHub UI)
• Addresses feedback and change requests
• Merges PR once approved (usually deletes branch unless develop or release)

👩‍💻 Reviewer

• Invited to review PR by Assignee (via GitHub UI)
• Is expected to complete a review and address followup

[blaketarter]

Nice work!