[fix](ci) Increase automated code review timeout to 120 minutes

[shuke987]

What problem does this PR solve?

Problem Summary:

The automated review of #67687 hit the 90-minute step timeout while finishing its report (failed run); its formal review was submitted about 23 seconds later.

Increase the review step timeout from 90 to 120 minutes. Raise the job timeout from 208 to 238 minutes and update the budget comment, preserving 8 minutes for auth synchronization and 12 minutes for runner setup and post-job cleanup.

Release note

None

Check List (For Author)

• Test:
  • Unit Test: all 18 existing test_review_auth_quarantine.py tests passed against the modified workflow using fake OSS, Codex, and GitHub services.
  • Manual test: parsed the YAML and verified the 120-minute review limit, 218-minute pre-finalization budget, 8-minute auth sync, and 12-minute reserve within the 238-minute job limit. Confirmed no other parsed workflow changes; patch whitespace check passed.
• Behavior changed:
  • Yes. Automated reviews may run for up to 120 minutes.
• Does this need documentation?
  • No. The workflow budget comment is updated.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[shuke987]

skip buildall