feat/930-extend-toNewsKitIcon-types

[KayKostadinov]

closes #930

What

1. Background - why this is needed
   This is needed due to an update in the https://github.com/emotion-icons package. Bootstrapping a project with node 18 and react types 18 resolves the type EmotionIcon for the emotion icons. This results is a type error when passing them to the toNewsKitIcon transformer function.

2. What did you do
   Extend toNewsKitIcon parameter types to include EmotionIcon.

3. What does the reviewers should expect

I have done:

• Written unit tests against changes
• Written functional tests against the component and/or NewsKit site
• Updated relevant documentation

I have tested manually:

• The feature's functionality is working as expected on Chrome, Firefox, Safari and Edge
• The screen reader reads and flows through the elements as expected.
• There are no new errors in the browser console coming from this PR.
• When visual test is not added, it renders correctly on different browsers and mobile viewports (Safari, Firefox, small mobile viewport, tablet)
• The Playground feature is working as expected

Before:

After:

Who should review this PR:

How to test:

[pp-serviceaccount]

You can preview these changes on:
Documentation Site: http://ncu-newskit-docs-pr.s3-website-eu-west-1.amazonaws.com/930-extend-tonewskiticon-types
Storybook: http://ncu-newskit-docs-pr.s3-website-eu-west-1.amazonaws.com/930-extend-tonewskiticon-types/storybook

[KayKostadinov]

I've added these because the component loads dynamically brightcove video players with repeating aria IDs and this is flagged by the accessibility tests. I can see the same rules were disabled for "title": "video player" component, likely due to the same reason. Since this is loaded by a runtime script the test is flaky.