Update coderabbit configuration

Author: fizyk

.coderabbit.yaml

@@ -11,8 +11,9 @@ reviews:
         3. Content must be a clear, concise description of the change
         4. Content should be suitable for inclusion in CHANGES.rst
         5. Verify the type matches the nature of the change based on towncrier type definitions
-        6. Flag any files with invalid types or malformed filenames
-        7. Check that the description is meaningful (not just "fix" or "update")
+        6. Some changes may require multiple types. Especially breaking changes
+        7. Flag any files with invalid types or malformed filenames
+        8. Check that the description is meaningful (not just "fix" or "update")
 
   pre_merge_checks:
     custom_checks:
@@ -22,6 +23,6 @@ reviews:
           Check if a newsfragment file has been added to the newsfragments/ directory.
           Read the towncrier configuration from pyproject.toml to determine valid newsfragment types.
           If no newsfragment is present, suggest which type should be added based on the PR changes.
-          Suggest the filename format: [issue_or_pr_number].[type].rst
-          Remind contributors to use: `pipenv run towncrier create [number].[type].rst`
+          Suggest the filename format: [issue_or_pr_number].[type].rst (or +[hash].[type].rst for orphan fragments)
+          Remind contributors to use: `pipenv run towncrier create [number].[type].rst` (or `pipenv run towncrier create +.[type]` for orphan fragments)
           Skip the check if the PR only updates existing newsfragments or is a trivial change.