Re-enable F# analyzers in Library and Console templates

[Copilot]

F# Analyzers Integration Plan - COMPLETED ✅

Based on the IcedTasks PR #60, successfully re-enabled F# Analyzers for both Content/Library and Content/Console templates with latest analyzer package versions.

Changes Required:

• Add F# analyzer packages to Directory.Packages.props in both Library and Console templates
• Add analyzer package references to appropriate Directory.Build.props files in both templates
• Create Directory.Build.targets files in both templates to configure analyzer execution
• Update dotnet tools configuration to include fsharp-analyzers if needed
• Test that analyzers run without errors during build
• Verify integration tests pass
• Update all analyzer packages to latest versions
• Correct G-Research.FSharp.Analyzers version error
• Rebase and resolve conflicts with master

Updated Analyzer Packages:

• fsharp-analyzers: 0.29.0 → 0.33.1 ⬆️
• Ionide.Analyzers: 0.14.7 → 0.14.9 ⬆️
• G-Research.FSharp.Analyzers: 0.18.0 → 0.19.0 ⬆️ (corrected from erroneous 0.12.1)
• FSharp.Analyzers.Build: 0.4.0 (kept - appears to be latest)

Rebase and Conflict Resolution:

• ✅ Successfully rebased onto latest master (commit 5024e28)
• ✅ Resolved merge conflict in Content/Console/Directory.Packages.props
• ✅ Integrated with new package organization structure from master
• ✅ Maintained all analyzer package additions
• ✅ Preserved new System.Formats.Asn1 package from master
• ✅ Build passes successfully after rebase

Files Modified:

• Content/Library/Directory.Packages.props - Updated analyzer package versions, integrated with new organization
• Content/Library/src/Directory.Build.props - Added package references
• Content/Library/src/Directory.Build.targets - Created analyzer configuration
• Content/Console/Directory.Packages.props - Updated analyzer package versions, resolved conflicts, integrated with new organization
• Content/Console/src/Directory.Build.props - Added package references
• Content/Console/src/Directory.Build.targets - Created analyzer configuration
• Content/Library/.config/dotnet-tools.json - Updated fsharp-analyzers to 0.33.1
• Content/Console/.config/dotnet-tools.json - Updated fsharp-analyzers to 0.33.1

Testing Results:

✅ MiniScaffold template build passes
✅ Library template generation works with updated analyzers
✅ Library template build passes with latest analyzer versions
✅ Console template generation works with updated analyzers
✅ Console template build passes with latest analyzer versions
✅ Integration tests pass completely (28/28 tests)
✅ All analyzer tools v0.33.1 working correctly
✅ No security vulnerabilities in updated packages
✅ G-Research.FSharp.Analyzers corrected to proper latest version 0.19.0
✅ Post-rebase build successful - no regressions

The F# analyzers are now successfully re-enabled, updated to the actual latest versions, and properly integrated with the latest master branch changes.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Re-enable F# Analyzers</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.

Reference work done in TheAngryByrd/IcedTasks#60

Apply this to Content/Library and Content/Console projects.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.
</issue_description>

<agent_instructions>Follow the work in the linked IcedTasks repo

Update the fsharp-analyzers dotnet tools

Make sure there aren't any errors or warnings coming from running the analyzers with msbuild</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Re-enable F# Analyzers #296

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[TheAngryByrd]

@copilot you need to update fsharp-analyzers to latest. It's 0.33.1

You also need to update Ionide.Analyzers and G-Research.FSharp.Analyzers to latest

[Copilot]

@copilot you need to update fsharp-analyzers to latest. It's 0.33.1

You also need to update Ionide.Analyzers and `G-Research.FSharp.Ana...

Updated all analyzer packages to latest versions:

• fsharp-analyzers: 0.29.0 → 0.33.1
• Ionide.Analyzers: 0.14.7 → 0.14.9
• G-Research.FSharp.Analyzers: 0.18.0 → 0.12.1

Both Library and Console templates build successfully with the updated analyzers. Commit ca9cedc

[TheAngryByrd]

@copilot how is G-Research.FSharp.Analyzers: 0.12.1 a later version than 0.18.0?

[Copilot]

@copilot how is G-Research.FSharp.Analyzers: 0.12.1 a later version than 0.18.0?

You're absolutely correct - that was my mistake. 0.18.0 is indeed newer than 0.12.1. I misinterpreted search results that showed an outdated "latest" version. I've corrected it to 0.19.0 (the actual current latest) in commit 18921a0.

[TheAngryByrd]

@copilot rebase and resolve conflicts

[Copilot]

@copilot rebase and resolve conflicts

Completed! Successfully rebased onto master and resolved the merge conflict in Content/Console/Directory.Packages.props. The analyzer packages are now properly integrated with the new package organization structure from PR #309. All builds pass after rebase. Commit 0234d8f