ci: Add config file for CodeRabbit with custom rules

[spetrosi]

Sourcery that we currently use cannot read documentation files and best
practices, it's rather a refactoring tool.
So I want to introduce CodeRabbit that allows creating .coderabbit.yaml with
custom rules and conventions.

Signed-off-by: Sergei Petrosian spetrosi@redhat.com

Summary by Sourcery

Add a CodeRabbit configuration file to enforce repository-specific review rules and conventions.

CI:

• Configure CodeRabbit review settings, disabling non-essential features and enabling checks for PR titles and descriptions.

Documentation:

• Document coding, testing, and documentation conventions for different file types via CodeRabbit path-specific review instructions.

Chores:

• Centralize role- and project-specific automation guidelines in a shared, auto-managed .coderabbit.yaml file.

[sourcery-ai]

Reviewer's Guide

Adds a CodeRabbit configuration file to enforce repository-specific PR conventions and give CodeRabbit detailed, path-based review instructions for Ansible roles, tests, templates, variables, Python code, and documentation, while disabling non-essential CodeRabbit features.

Sequence diagram for CodeRabbit review flow using .coderabbit.yaml

sequenceDiagram
  title CodeRabbit review sequence using .coderabbit_yaml
  actor Developer
  participant GitHub
  participant CodeRabbit
  participant CodeRabbitConfig

  Developer->>GitHub: push code
  GitHub->>CodeRabbit: trigger review
  CodeRabbit->>CodeRabbitConfig: read config
  CodeRabbitConfig-->>CodeRabbit: return config
  CodeRabbit-->>GitHub: post review
  GitHub-->>Developer: show review

Loading

File-Level Changes

Change	Details	Files
Introduce CodeRabbit configuration with tailored review behavior and project-specific conventions.	Create .coderabbit.yaml with top-level chat and reviews configuration, disabling fun/auto features and finishing touches such as unit test suggestions. Define pre-merge checks that warn on PR titles not following Conventional Commits and descriptions not following the repository pull request template. Add path-based review instructions for Ansible tasks, handlers, tests, templates, defaults, vars, Python files, and README to encode existing best practices and testing/documentation requirements.	.coderabbit.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path=".coderabbit.yaml" line_range="191-195" />
<code_context>
+    # ========================================
+    # Templates
+    # ========================================
+    - path: "templates/**/*.j2"
+      instructions: |
+        **Required headers (in this order):**
+        1. ansible_managed header: `{{ ansible_managed | comment }}`
+        2. Role fingerprint: `{{ "system_role:ssh" | comment(prefix="", postfix="") }}`
+
+    # ========================================
</code_context>
<issue_to_address>
**issue (bug_risk):** Hard-coded `system_role:ssh` fingerprint may be incorrect for non-ssh roles using this shared config.

Because this config is shared for `linux-system-roles`, using `system_role:ssh` here will generate the wrong fingerprint for any non-ssh role that uses it. Please either make the role name configurable (if templating is supported in per-repo overrides) or move the fingerprint header into per-role overrides so each role can define its own `system_role:<role_name>` value.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): Hard-coded system_role:ssh fingerprint may be incorrect for non-ssh roles using this shared config.

Because this config is shared for linux-system-roles, using system_role:ssh here will generate the wrong fingerprint for any non-ssh role that uses it. Please either make the role name configurable (if templating is supported in per-repo overrides) or move the fingerprint header into per-role overrides so each role can define its own system_role:<role_name> value.