Tooltip provider for easily sharing tooltip amongst multiple elements

[gabrieljablonski]

Closes #837
Closes #847

Using just anchorId without the provider should still work fine.
See App.tsx for usage example.

The only major feature missing is using a prop such as data-tooltip-id on the anchor element and filtering the event listener and observer subscriptions by the tooltip id.
The provider also has to keep the anchorRefs and activeAnchor separate by tooltip id.

Instead of using data-tooltip-id, it would also be possible to change the context data signature to something such as

interface TooltipContextData {
  getAnchorRefs: (tooltipId?: string) => Set<React.RefObject<HTMLElement>>
  attach: (...ref: React.RefObject<HTMLElement>[], tooltipId?: string) => void
  detach: (...ref: React.RefObject<HTMLElement>[], tooltipId?: string) => void
  getActiveAnchor: (tooltipId?: string) => React.RefObject<HTMLElement>
  setActiveAnchor: React.Dispatch<React.SetStateAction<React.RefObject<HTMLElement>>>
}

tooltipId is used to keep track of which tooltip is being accessed.

Without a change like one of these two, the provider only works with one <Tooltip /> element.

If needed, multiple providers (one <Tooltip /> inside each) can be separately used as a workaround.

[danielbarion]

The looks nice to me, but only 2 things:

I believe we should use explicit words, like event instead of e.

And can you create docs inside docs folder related to the new possibility of use of the Tooltip, please?

[gabrieljablonski]

After some testing, I've realized cloneElement() doesn't work super well when passing functional components as children to the wrapper.

Using an actual DOM element (span seems ok) didn't seem to cause any issues.

[danielbarion]

looks good to me!