chore(components): refactor InteractivePopover to take a type argument for the trigger element

[kraenhansen]

Description

As a follow-up to this #6486 (comment), I suggest adding a type argument to the InteractivePopover to specify the concrete HTMLElement used when declaring the type of the ref passed through the trigger callback.

We can't just pass React.Ref<HTMLElement> as that (as an example) isn't possible to pass via ref to a <button />:

const ref = React.useRef<HTMLElement>(null);
return <button ref={ref} />;

☝️ yields this TS error related to the ref prop:

Type 'RefObject<HTMLElement>' is not assignable to type 'LegacyRef<HTMLButtonElement> | undefined'.
  Type 'RefObject<HTMLElement>' is not assignable to type 'RefObject<HTMLButtonElement>'.
    Type 'HTMLElement' is missing the following properties from type 'HTMLButtonElement': disabled, form, formAction, formEnctype, and 15 more.ts(2322)

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[kraenhansen]

This could have followed a pattern and be named T but it felt a bit too vague 🤔

[kraenhansen]

I believe it's possible to pass the ref here without having to provide an explicit type parameter to the InteractivePopover above, is possible because the IconButton use the forwardRef utility internally.

[gribnoysup]

Neat, thanks for the follow up to clean this up!