Fix init-windows template to automatically detect existing codegen spec files

[Copilot]

• Analyze the issue with hardcoded codegen includes in init-windows template
• Scan codegen directory for existing spec files during template generation
• Update template to use actual filenames when existing spec files are found
• Add fallback to conditional includes when no existing files are present
• Test the solution with existing projects
• Add explanatory comments about Mustache template syntax for C++ developers

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Microsoft Reviewers: Open in CodeFlow

[anupriya13]

@copilot don't add a comment for developer to fix, we need to get the correct file name from..\codegen\<filename>.g.hfile

[Copilot]

@copilot don't add a comment for developer to fix, we need to get the correct file name from..\codegen\<filename>.g.hfile

I've updated the solution to automatically detect existing codegen spec files instead of using TODO comments. The template now:

1. Scans the windows/{projectName}/codegen/ directory for existing *Spec.g.h files during template generation
2. If existing spec files are found, uses the actual filename and extracted module name
3. Falls back to conditional __has_include checks when no existing files are found

This eliminates the need for manual developer intervention while handling both scenarios correctly. (commit b02696d)

[sundaramramaswamy]

LGTM!

[sundaramramaswamy]

@copilot Please add a preceding comment about these Mustache template nuances as these are foreign to regular C++ programmers.

[Copilot]

Added explanatory comments about the Mustache template syntax before both conditional include blocks to help C++ developers understand that these constructs will be processed during project generation. (commit a098073)

[sundaramramaswamy]

LGTM

[sundaramramaswamy]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).