[Feature]: Add secondary content to Tooltip

User story

As a user, I want tooltips to distinguish primary and supporting content so that the main label stays concise and secondary information remains easy to scan.

Teams currently includes supporting information such as keyboard shortcuts in parentheses as part of tooltip labels. This mixes the main label with secondary information. Menu items already provide a secondaryContent slot; Tooltip should offer the same content hierarchy and visual pattern.

Proposed behavior

• Add an optional secondaryContent slot to Tooltip.
• Render it opposite the primary content, consistent with MenuItem.
• Keep existing Tooltip rendering unchanged when secondaryContent is absent.
• Document keyboard shortcuts as one common use case without making the API shortcut-specific.
• Support wrapping, RTL, dark mode, and high contrast.

Acceptance criteria

• secondaryContent is a public slot and participates in the accessible label or description, matching MenuItem behavior.
• Primary and secondary content render on one row when space permits and wrap cleanly when constrained.
• Existing Tooltip consumers have no DOM or visual change unless they use the new slot.
• Unit, Storybook, and visual-regression coverage are included.

Example

<Tooltip content="Bold" secondaryContent="Ctrl+B" relationship="label">
  <Button icon={<TextBoldRegular />} />
</Tooltip>

Preview