only render portal when the element is actually needed to be displayed

[Kiarokh]

fix https://github.com/Lundalogik/crm-feature/issues/3703
fix #2583

Review:

• Commits are atomic
• Commits have the correct type for the changes made
• Commits with breaking changes are marked as such

Browsers tested:

(Check any that applies, it's ok to leave boxes unchecked if testing something didn't seem relevant.)

Windows:

• Chrome
• Edge
• Firefox

Linux:

• Chrome
• Firefox

macOS:

• Chrome
• Firefox
• Safari

Mobile:

• Chrome on Android
• iOS

[github-actions]

Documentation has been published to https://lundalogik.github.io/lime-elements/versions/PR-2589/

[john-traas]

After investigating the side effects of these proposed changes, it seems to unlock potential issues and bugs that could have wide reaching effects.

Some of the potential bugs discovered are potential infinite-loops and intersection observers that are expecting to see an element, which is now not present in the DOM (since with these changes we would hold off rendering the portal if the element is not open).

Much as it might be inefficient to have so many instances of the portal open, it is the underlying structure on which much of the web client is currently built.

With these proposed changes, errors occur in other components specifically with the intersection observer. I think we're opening a potential rabbit hole here and I don't believe the rewards are worth the risk.