MPT-16808: add CodeRabbit config and copilot-instructions

[svazquezco]

Closes MPT-16808

• Introduce .coderabbit.yaml configuration file with schema definition and remote configuration reference
• Add comprehensive Python coding guidelines and workflow instructions in .github/workflows/copilot-instructions.md, covering conventions for type hints, docstrings, testing practices, linting standards, and development workflow
• Remove the Danger GitHub Actions workflow (.github/workflows/danger.yml)

[coderabbitai]

📝 Walkthrough

Walkthrough

Introduces a new .coderabbit.yaml configuration file with remote config reference, adds Python coding conventions and workflow guidelines documentation, and removes the Danger GitHub Actions workflow.

Changes

Cohort / File(s)	Summary
Configuration \.coderabbit\.yaml	New configuration file added with YAML schema header and remote_config section pointing to external configuration URL
Documentation \.github/workflows/copilot-instructions\.md	New guidelines documentation specifying Python coding conventions, environment-variable configuration, versioning rules, type hints, docstring format (Google-style), testing practices (pytest, AAA pattern, fixtures, mocking), and linter preferences (Ruff primary, Flake8 for specific checks)
Workflow Removal \.github/workflows/danger\.yml	Removed DangerCI GitHub Actions workflow that performed PR checks on pull_request events with read contents and write PR permissions

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Jira Issue Key In Title	✅ Passed	The PR title contains exactly one Jira issue key MPT-16808 in the correct format.
Test Coverage Required	✅ Passed	This PR modifies only configuration files (.coderabbit.yaml, .github/workflows/danger.yml) and documentation (.github/workflows/copilot-instructions.md), not executable source code.
Single Commit Required	✅ Passed	The pull request contains exactly one commit (507d322: feat: add CodeRabbit config and copilot-instructions), which meets the requirement of maintaining a clean git history with a single commit per PR.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/copilot-instructions.md:
- Around line 12-15: The versioning examples in the workflow doc are ambiguous
about which package manager syntax is intended; update the text to first state
which dependency management tool the project uses (e.g., Poetry or
pip/pip-tools) and then show the correct examples for that tool: for Poetry use
pyproject.toml style like django = "4.2.*" or django = "^4.2.0" (caret is valid
in Poetry), and for pip/requirements use django==4.2.*; replace the current
misleading lines (`django==4.2.*` and `django==^4.2.2`) with the appropriate
examples and explicitly label each example with the tool it applies to.

📜 Review details

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 67fe877 and 507d322.

📒 Files selected for processing (3)

• .coderabbit.yaml
• .github/workflows/copilot-instructions.md
• .github/workflows/danger.yml

💤 Files with no reviewable changes (1)

• .github/workflows/danger.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (4)

.github/workflows/copilot-instructions.md (3)

1-4: LGTM!

The front matter correctly defines the scope and purpose of these coding guidelines.

---

19-30: LGTM!

The Python coding standards are well-defined and follow modern best practices. The combination of Ruff for general linting and Flake8 for specialized plugins (wemake-python-styleguide, flake8-aaa) is a solid approach.

---

32-43: LGTM!

The testing guidelines are comprehensive and enforce best practices. Particularly good are:

• Strict AAA pattern enforcement
• Mandatory use of spec/autospec for mocks (prevents common mocking pitfalls)
• Prohibition of branching logic in tests (keeps tests simple and predictable)

.coderabbit.yaml (1)

2-3: Remote config URL is accessible, but consider pinning to a stable reference for reliability.

The remote config file is successfully retrieved and contains a valid CodeRabbit configuration. However, using the main branch creates an implicit dependency that could cause unexpected behavior changes if the remote configuration is modified. Consider pinning to a specific commit SHA or tag instead of main for better stability and predictability.

[svazquezco]

@coderabbitai resolve

[coderabbitai]

✅ Actions performed

Comments resolved and changes approved.