chore: remove ids from tooltips

[uinstinct]

Description

Initially TooTips required to have an id associated with 2 elements to display it. This required 2 independent elements one with id and another with data-tooltip-id.
This PR introduces a single Tooltip which removes the usage of id and the displaying element can be passed as children to the tooltip

• refactors ToolTips to match new props
• keeps all of the UI and other content the same

resolves CON-3586

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-general-review or @continue-detailed-review

Checklist

• [] I've read the contributing guide
• [] The relevant docs, if any, have been updated or created
• [] The relevant tests, if any, have been updated or created

Screen recording or screenshot

[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]

Tests

[ What tests were added or updated to ensure the changes work as expected? ]

---

Summary by cubic

Replaced id-based tooltip wiring with a simpler, id-less API. Tooltips now wrap the trigger element and accept content directly, keeping UI and behavior the same.

• Refactors

  • New API: {trigger} with auto-generated ids.
  • Removed data-tooltip-id and id usage across components.
  • Preserves existing options (place, className, style, clickable, delays).
  • Simplified helpers (e.g., InfoHover now accepts msg as a string).

• Migration

  • Wrap the target element with instead of pairing an element with data-tooltip-id and a separate .
  • Move any previous tooltip children into the content prop.
  • Update InfoHover to pass msg as a string.

[tomasz-stefaniak]

Just a sanity check - have you verified that this doesn't change the layout? It could, result in a slightly different HTML and alignment issues, I want to make sure it's been visually inspected before merging.

[uinstinct]

Just a sanity check - have you verified that this doesn't change the layout? It could, result in a slightly different HTML and alignment issues, I want to make sure it's been visually inspected before merging.

Yes! I checked most of them including simple ones, nested divs inside tooltips, hidden properties, clickables, etc.
All seem to be working fine!