fix: Fixing ComponentType props

[jnumainville]

Part of work for DH-19416 and a followup from #2477

If no props are specified for React.ComponentType it defaults to {}, allowing no props. We need to specify that we can have any.

[mofojed]

For these two types it'd be better to type the props with a Generic. See how we do it ComponentUtils, but would be something like this:

export type ElementPluginMappingDefinition<P extends Record<string, unknown> = {}> = Record<ElementName, React.ComponentType<P>>;

We get better typing that way when using it, and we don't need to use any.

[jnumainville]

I think I've got something generic working now

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.67%. Comparing base (5d15019) to head (8a9c3f2).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2498   +/-   ##
=======================================
  Coverage   44.67%   44.67%           
=======================================
  Files         762      762           
  Lines       42617    42617           
  Branches    10710    10710           
=======================================
  Hits        19038    19038           
  Misses      23568    23568           
  Partials       11       11           

Flag	Coverage Δ
unit	44.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mofojed]

As long as you've tried this in your template and it's working then I think we're good.

[jnumainville]

Yep I don't see any errors with the generated template