fix(Tooltip): add strategy option to support edge use cases

[pallendes]

Description

This PR adds the option of wrapping the tooltip inside a portal to fix some edge use cases.

Checklist

• Change increases quality
• Change is validated by tests
• Change is readable and easy to understand
• Documentation is updated
• Security impact has been considered
• Changes validated in runtime

[linear]

PLA-930 Migrate from abusix-ui to hailstorm

[rodelta]

LGTM, no stoppers.
A couple of questions, though.

• Would it work/help if we did tooltips always via portals? if that logic works for all cases, maybe it would be better for it to be the only strategy.
• Would be nice to have a case in storybook for quick checks that the thing is building properly

[pallendes]

LGTM, no stoppers. A couple of questions, though.

• Would it work/help if we did tooltips always via portals? if that logic works for all cases, maybe it would be better for it to be the only strategy.
• Would be nice to have a case in storybook for quick checks that the thing is building properly

1. I didn't want to leave it always to use portals, as it will add extra complexity to the rendering when, in most cases, using a portal is not needed, or just the "fixed" strategy can do the trick. Also, I can't be sure that using it inside a portal will work for all cases, as we can find more scenarios where it might not work for any reason. Therefore, I went for the more flexible alternative.

2. What do you mean by a case in a storybook? You can check all the possible scenarios by playing with the arguments in the documentation. Adding a specific case for portal strategy won't produce any visual difference.

[abusix-bot]

🎉 This PR is included in version 3.8.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀