A Pull Request should be associated with an Issue.

Related issue: #1484

Further notes in https://github.com/github/gh-ost/blob/master/.github/CONTRIBUTING.md
Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR

Description

Support for Ignoring Binlog Events Beyond Chunk Boundary Values
If the unique key value in a binlog event surpasses the maximum value defined for chunk iteration but remains below the overall maximum boundary for copying, the event is ignored. This approach is inspired by the design concept from shaohk's feat binlog apply optimization. We have implemented the functionality to ignore such binlog events based on the code from release v1.1.7.

Dynamic Expansion of Maximum Copy Boundary Values
To prevent issues arising from the interchangeable use of "copy rows" and "apply events" during gh-ost processes, which can lead to Table Space Bloat Due to Gh-ost #1484, we have introduced a mechanism to dynamically expand the maximum boundary value for copying. By ignoring large unique key insert events, this solution potentially mitigates the problem.

In case this PR introduced Go code changes:

• contributed code is using same conventions as original code
• script/cibuild returns with no formatting errors, build errors or unit test errors.