feat(react): add generic type parameter to useIonModal and useIonPopover

[EduardF1]

Summary

Adds generic type parameters to useIonModal and useIonPopover so TypeScript can infer the correct type for componentProps based on the component argument.

Motivation

Currently both hooks accept componentProps?: any, providing no type safety. This causes undetected typos in prop names and incorrect types at compile time.

Changes

• useIonModal and useIonPopover now have two overloaded signatures:
  1. When a React.ComponentClass<T> or React.FC<T> is passed, componentProps is typed as T
  2. When a JSX.Element is passed, componentProps remains any
• The implementation signature remains (component: ReactComponentOrElement, componentProps?: any) for backward compatibility
• The // TODO(FW-2959): types comment is removed as this resolves that TODO
• Default type parameter is Record<string, any> to preserve backward compatibility when no generic is specified

Testing

No runtime behavior changes — this is a type-only change. Existing tests should continue to pass.

Closes #28680

[vercel]

@EduardF1 is attempting to deploy a commit to the Ionic Team on Vercel.

A member of the Team first needs to authorize it.

[EduardF1]

It looks like the only failing check here is the Vercel preview deployment (Authorization required to deploy), which is expected for external contributors who do not have access to the Ionic Vercel team/deploy token.

All other current CI checks are passing. A maintainer can re-run/authorize the Vercel deployment if needed, or treat this preview check as non-blocking / not required for merge.

[EduardF1]

Quick follow-up: I do not see any maintainer reply yet. From my side this still looks ready apart from the Vercel authorization gate, which external contributors cannot unblock directly. Happy to address any code feedback once someone has a chance to review.