BigtableIO: Force minimum value of desiredBundleSizeBytes to be 1

[joar]

Fixes #28793 in the way suggested in #28793 (comment):

• BoundedReadEvaluatorFactory#getInitialInputs may still calculate a bytesPerBundle of 0 (e.g. when targetParallelism > estimatedBytes); but
• BigtableSource#split will interpret it as 1 in order to not violate the checkArgument() in

  beam/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigtable/BigtableIO.java

  Lines 1623 to 1626 in 71c8459

  	checkArgument(
  	desiredBundleSizeBytes > 0,
  	"Desired bundle size %s bytes must be greater than 0.",
  	desiredBundleSizeBytes);

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @bvolpato for label java.
R: @chamikaramj for label io.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[bvolpato]

Fix LGTM, just +1 on moving the CHANGES.md delta to 2.52.0 since 2.51.0 is almost out / at release candidate fix.

[joar]

The "PreCommit Whitespace" failure seems to me to be unrelated to the changes in this PR:

> Task :sdks:python:sdist

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':sdks:python:test-suites:tox:py38:archiveFilesToLint' (type 'Zip').
  - Gradle detected a problem with the following location: '/runner/_work/beam/beam'.
    
    Reason: Task ':sdks:python:test-suites:tox:py38:archiveFilesToLint' uses this output of task ':sdks:python:setupVirtualenv' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':sdks:python:setupVirtualenv' as an input of ':sdks:python:test-suites:tox:py38:archiveFilesToLint'.
      2. Declare an explicit dependency on ':sdks:python:setupVirtualenv' from ':sdks:python:test-suites:tox:py38:archiveFilesToLint' using Task#dependsOn.
      3. Declare an explicit dependency on ':sdks:python:setupVirtualenv' from ':sdks:python:test-suites:tox:py38:archiveFilesToLint' using Task#mustRunAfter.
    
    For more information, please refer to https://docs.gradle.org/8.3/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.

Edit: It could also be caused by the modifications to CHANGES.md, in which case it's not a great error message.
Edit 2: So, the changes to CHANGES.md seems to trigger the action, but the action itself seems broken at the moment.

[joar]

Running whitespacelint manually makes me believe that it would pass if the check was working :)

$ python -m pip install --user whitespacelint==1.1.0
Requirement already satisfied: whitespacelint==1.1.0 in /home/joar/.local/lib/python3.8/site-packages (1.1.0)
$ whitespacelint CHANGES.md
# exits with 0
$ git rev-parse HEAD
3096265e05ff59ae192cc7f4a571e9247937211b

[Abacn]

whitespace issue was an issue on master and now fixed #28845