chore: dummy change to be cherry-picked with conflict

[maybe-vibe]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

• Closes #[ISSUE_NUMBER]

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• I have checked the Release Timeline and Currently Supported Versions to determine which release branches I need to cherry-pick this PR into.

Documentation

• My PR needs documentation updates.

Release note

[github-actions]

❌ Cherry-pick failed for one or more branches. Please check the workflow run logs and consider retrying or manually cherry-picking.

[github-actions]

✅ Cherry-pick PRs (or issues if encountered conflicts) have been created successfully to all target branches.

[github-actions]

❌ Cherry-pick failed for one or more branches. Please check the workflow run logs and consider retrying or manually cherry-picking.

[github-actions]

❌ Cherry-pick failed for one or more branches. Please check the workflow run logs and consider retrying or manually cherry-picking.

[github-actions]

❌ Cherry-pick failed for one or more branches. Please check the workflow run logs and consider retrying or manually cherry-picking.

[github-actions]

❌ Cherry-pick failed for one or more branches. Please check the workflow run logs and consider retrying or manually cherry-picking.