Popper JS memory leak issues

[GCHQ-Developer-530]

Summary of the bug

Popper JS is causing memory leak issues.

🪜 How to reproduce

Popper is adding scroll and resize event listeners to the window. The event handler triggers a Popper forceUpdate on scroll which is expensive and blocks the scroll which is the reason for the performance issue. The Stencil issue we thought it was (#682) compounds the Popper issue as none of these event listeners are being removed.

Looks like someone has spotted a memory leak issue in the tutorial and we've followed that. floating-ui/popper.js.org#47 This has been tried and doesn't fix our memory leak issues by itself, but will probably still need changing.

Could either be updating how we add and remove event listeners, or we may need to look into converting to floating ui which could turn out to be a lot of work.

🧐 Expected behaviour

No performance issues.

[ad9242]

May be possible to turn off the scroll listener? https://popper.js.org/docs/v2/modifiers/event-listeners/

Or at very least it should not add the event listeners if disableTooltip is set to true. At the moment that prop only determines the visibility