[Improve][Connector-V2][HBase] Support configurable range scan boundary inclusion policies

[zhangshenghang]

Purpose of this pull request

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config

[davidzollo]

+1

[xiaochen-zhou]

In order to maintain consistency with the previous logic, i think the default value of end_row_inclusive should also be true.

[zhangshenghang]

thanks @xiaochen-zhou suggest, to ensure that data can be read normally without duplication, we need to include only one side.

[Carl-Zhou-CN]

hi,Will the data be duplicated when both END_ROW_INCLUSIVE and START_ROW_INCLUSIVE are true？

[Carl-Zhou-CN]

I think the intended result of the configuration should be to control whether the boundaries are included. However, I believe that when both sides are set to false, it will result in shards like (start, 1), (1, 3), (3, end), which causes the loss of boundary data. Conversely, it will lead to duplicate boundary data. Instead of adjusting the boundaries of each split, we should only modify the inclusion settings of the start and end points