Modify PR Process md File to Clarify Addressing Roomote and Automated Comments

[j-east]

Problem (one or two sentences)

https://github.com/RooCodeInc/Roo-Code/blob/main/CONTRIBUTING.md#3-submitting-code-pull-request-pr-process

As the automated review process improves we need to update the contribution guidelines to resolve automated comments on PR. (Comment on why proposed changes are not needed or commit changes to resolve)

Context (who is affected and when)

OSS Contributors

Desired behavior (conceptual, not technical)

Modify Readme

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I'm exploring a potential fix for updating the CONTRIBUTING.md file to clarify how to address automated review comments. I'll open a PR to share progress.

[roomote]

Opened PR #8534 with my attempt at addressing this issue. The PR adds a new section to CONTRIBUTING.md that clarifies how contributors should handle automated review comments. All CI checks have passed. Feedback welcome!

PR link: #8534

[daniel-lxs]

The decision on whether an automated comment must be addressed before merging is up to the maintainer reviewing the PR.
For now, automated comments can be optionally addressed, but if a maintainer requests that a specific comment be resolved, it should be addressed before the PR is merged.

Thank you for writing this up!