use wildcard (*) to match "revealed" trigger when scrolling

[danielnieto]

Description

Fixes #2233, using wildcard to match "revealed" trigger when collecting elements to execute maybeReveal on while scrolling allows using more events in the same hx-trigger attribute (i.e. click, mouseenter, custom events, etc)

A minimal example to reproduce the bug is included in the original issue.

Corresponding issue: #2233

Testing

The only way to test this is to have an element with hx-trigger="revealed, anyOtherEvent" below the fold (so that the initial maybeReveal function would not trigger the request)

I've updated scroll-test-eventHandler.html manual test to include 3 cases (at the very bottom), when the reveal event appears first, when it's last and when it's in the middle. All of them working after applying the fix.

Checklist

• I have read the contribution guidelines
• I have targeted this PR against the correct branch (master for website changes, dev for
  source changes)
• This is either a bugfix, a documentation update, or a new feature that has been explicitly
  approved via an issue
• I ran the test suite locally (npm run test) and verified that it succeeded

[carducci]

Grateful for this pull request. I've been running this patched version in production for a couple of months. Many thanks to the authors and contributors in this community!