chore(ci): fix gen next patch release

[everpcpc]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[what-the-diff]

PR Summary

• Improved Clarity in Version Bumping Code

  • We made changes to the 'bump_version.js', focusing on refining how we handle version updates. This should not only make the version updating process straightforward but will also avoid potential errors. We did this by making variable names clearer - for instance, renaming the variable 'patch' to 'version'.

• Enhancement of Pre-release Version Increment Logic

  • We revised the mechanism in incrementing the pre-release version number to be more accurate. This way, when a new version is in the works, the version number updates will precisely reflect where we are in our development stage. It was previously done by simply adding one (pv + 1), but now, we're adding one to the parsed version number (parseInt(version[4]) + 1).