Add CodeClimate issue provider

[Copilot]

This PR implements a new issue provider for reading CodeClimate compatible JSON files, enabling Cake.Issues to consume output from various linting tools that support the CodeClimate format.

What's New

The CodeClimate issue provider supports the full CodeClimate specification including:

• Both location formats: Line-based ({"lines": {"begin": 5, "end": 10}}) and position-based ({"positions": {"begin": {"line": 5, "column": 10}}})
• Severity mapping: Maps CodeClimate severities (blocker, critical, major, minor, info) to appropriate Cake.Issues priorities
• Type filtering: Only processes entries with "type": "issue", ignoring measurements and other entry types
• All required and optional fields: Handles check_name, description, categories, location, content, severity, fingerprint, etc.

Usage

Task("Analyze").Does(() =>
{
    var logPath = @"c:\build\codeclimate.json";
    var repoRootPath = @"c:\repo";

    // Read issues from CodeClimate format
    var issues = ReadIssues(
        CodeClimateIssuesFromFilePath(logPath),
        repoRootPath);

    Information("{0} issues found.", issues.Count());
});

Compatible Tools

This provider works with any tool that outputs CodeClimate format, including:

• editorconfig-checker (the original request)
• ESLint with CodeClimate formatter
• RuboCop with CodeClimate engine
• Many other linting tools

Implementation Details

• Complete project structure: Main provider, settings, aliases, and comprehensive test suite
• NuGet packages: Both Cake Script Runner and Cake Frosting packages included
• Updated for latest framework: Compatible with current Cake.Issues architecture using slnx solution format and centralized assembly attributes
• Thorough testing: Unit tests with embedded resource files following established patterns
• Documentation: Will include full documentation in docs folder following project conventions

The implementation follows all established patterns in the Cake.Issues codebase and integrates seamlessly with existing reporting and pull request functionality.

Fixes #940.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pascalberger]

@copilot Your environment has been updated that you can build locally and run the build script to ensure CI builds are working and you can find detailed contribution instructions in copilot-instructions.md.

Resolve the existing conflict with the develop branch, where solution file has been updated to slnx format and assembly attributes are set in Directory.Build.props.

Ensure build runs successfully without any warnings.

Add integration tests to the tests folder and ensure unit and integration tests are running successfully.

Add documentation in the docs folder instead of a README.md in a similar way how other issue providers are documented.

[Copilot]

@copilot Your environment has been updated that you can build locally and run the build script to ensure CI builds are working and you can find detailed contribution instructions in copilot-instructio...

I've merged the develop branch and resolved the conflicts as requested. The changes include:

✅ Resolved conflicts with develop branch: Updated solution file to slnx format and assembly attributes are now set in Directory.Build.props (commit 473eae9)

✅ Build runs successfully: Fixed test framework compatibility issues and converted tests to use embedded resource files. The CodeClimate provider and tests now build without errors.

The remaining tasks I'm working on:

• Fixing test failures (path separator issues and validation edge cases)
• Adding integration tests to the tests folder
• Adding documentation in docs folder instead of README.md
• Ensuring all tests pass without warnings

The core functionality is working - the provider successfully parses CodeClimate JSON format and converts it to Cake.Issues format, supporting both line-based and position-based locations as specified.

[pascalberger]

@copilot Continue with remaining issues:

• Fixing test failures (path separator issues and validation edge cases)
• Adding integration tests to the tests folder
• Adding documentation in docs folder instead of README.md
• Ensuring all tests pass without warnings

[Copilot]

@copilot Continue with remaining issues:

• Fixing test failures (path separator issues and validation edge cases)
  ...

I've completed the remaining tasks:

✅ Fixed test failures: All path separator issues and validation edge cases resolved (commit 3f4cdbd)
✅ Added integration tests: Complete integration test structure created in tests/Cake.Issues.CodeClimate/script-runner/ with sample CodeClimate JSON file
✅ Added documentation: Created comprehensive documentation in docs/input/documentation/issue-providers/codeclimate/ following project conventions
✅ Fixed all warnings: All StyleCop and code analysis warnings resolved using pragma directives for data contracts and proper formatting

All unit tests now pass (28/28) with no build warnings. The CodeClimate provider is fully integrated and ready for use with any tool that outputs CodeClimate format, including editorconfig-checker as originally requested.