Enhance reduce_boolean_decision to accommodate any-analogous semantics expected by EarlyStopping Callback

[speediedan]

What does this PR do?

Fixes #15252

When EarlyStopping is used in a distributed context, early stopping conditions may be met in some processes before others (especially when the divergence_threshold is sufficiently low).

Per the described intended behavior of EarlyStopping:
https://github.com/Lightning-AI/lightning/blob/be1eb5e86d07fe22b53a59184089aac569875117/src/pytorch_lightning/callbacks/early_stopping.py#L204-L205
, all training processes should be stopped when an EarlyStopping threshold is reached in any process. The current behavior of reduce_boolean_decision is to only return True when all input process decisions are True:
https://github.com/Lightning-AI/lightning/blob/be1eb5e86d07fe22b53a59184089aac569875117/src/lightning_lite/strategies/parallel.py#L88-L92

Though this issue can be avoided when logging the monitored metric with sync_dist=True, since that configuration is not mandatory, reduce_boolean_decision should be adapted to behave as the EarlyStopping callback expects.

This PR maintains the current reduce_boolean_decision behavior by default, but enhances the function to accommodate any-analogous semantics as expected by the EarlyStopping callback. This PR also includes an additional test to validate the aforementioned new behavior resolves the issue described.

Does your PR introduce any breaking changes? If yes, please list them.

None

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[codecov]

Codecov Report

Merging #15253 (0aed7c8) into master (be1eb5e) will increase coverage by 2%.
The diff coverage is 88%.

❗ Current head 0aed7c8 differs from pull request most recent head d2b61b2. Consider uploading reports for the commit d2b61b2 to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #15253     +/-   ##
=========================================
+ Coverage      82%      84%     +2%     
=========================================
  Files         413      288    -125     
  Lines       30463    22002   -8461     
=========================================
- Hits        24938    18387   -6551     
+ Misses       5525     3615   -1910