[BUGFIX beta] Enumerable#any bug - not always returning a boolean

[bryanaka]

closes #12533

Enumerable#any is supposed to return only a boolean, but is currently returning whatever truthy value is returned in the callback. This changed functionality is now aligned with Array#some.

Potentially a breaking change if someone was relying on the buggy functionality. It was introduced here - #4144

[bryanaka]

hate to be a bother, but was wondering if this PR is valid or not?

I know it has some possibly far-reaching consequences (people relying on the buggy behavior), and the fact that it may be removed with iterators and more of the newer Array functions like Array#some being so well supported.

I'm cc'ing original commenters on the #12533 @pixelhandler @Serabe

[homu]

☔ The latest upstream changes (presumably #13658) made this pull request unmergeable. Please resolve the merge conflicts.

[locks]

Thank you for this effort and sorry for having let it sit for so long 🙇.

I have to side with your argument about the possible breaking changes this bugfix will introduce.
Regardless of documentation or intent, the current behaviour of any is the defacto one, being in effect for nearly four years.
What I believe we have to do in this case is to address the documentation of any to mention this quick and move from any to some. There is already an RFC that intends to do this. Let's figure out the path forward there :)