feat(web-components): update second half of web-components files to resolve strict mode errors

[GCHQ-Developer-847]

Summary of the changes

Update second half of the web-components files to resolve strict mode errors (first half has been completed: #3328). Also added some unit tests as the changes brought the coverage below 80%.

Update: also added a new IcMultiValueEventDetail type to resolve ticket #3349 (have updated ic-select + ic-menu files to use this, and also one instance in ic-search-bar, as it uses ic-menu).

I have added the non-null assertion operator (!) after some variables. This is because those variables are component props which have a default value; the TypeScript strict mode checking doesn't seem to detect that these default values exist.

I will create a separate PR to actually enable TypeScript mode. (Enabling TypeScript mode causes | undefined to be added to every optional prop in the component readme files - want to avoid loads of changes in this PR so GitHub doesn't become really slow when viewing them).

Related issue

#266

Checklist

General

• Changes to docs package checked and committed.
• All acceptance criteria reviewed and met.

Testing

• Relevant unit tests and visual regression tests added.
• Visual testing against Figma component specification completed.
• Playground stories in React Storybook up to date, with any prop changes and additions addressed.
• Compare performance of modified components against develop using Performance addon in React Storybook.

Accessibility

• Accessibility Insights FastPass performed.
• A11y unit test added and yields no issues.
• A11y plug-in on Storybook yields no issues.
• Manual screen reader testing performed using NVDA and VoiceOver.
• Manual keyboard testing for keyboard controls and logical focus order.
• Correct roles used and ARIA attributes used correctly where required.
• Logical heading structure is maintained, and the HTML elements used for headings can be changed to fit within the wider page structure.

Resize/zoom behaviour

• Page can be zoomed to 400% with no loss of content.
• Screen magnifier used with no issues.
• Text resized to 200% with no loss of content.
• Text spacing increased as per the WCAG 1.4.12 success criterion with no loss of content.

System modes

• Browser setting 'prefers reduced motion' tested. No animations or motion visible whilst this setting is on.
• Windows High Contrast mode tested with no loss of content.
• System light and dark mode tested with no loss of content.
• Browser support tested (Chrome, Safari, Firefox and Edge).

Testing content extremes

• Min/max content examples tested with no loss of content or overflow.
• All prop combinations work without issue.
• Tested for FOUC (Flash of Unstyled Content) in both SSR (Server-Side Rendering) and SSG (Static Site Generation) settings.
• Controlled and uncontrolled input components tested.
• Props/slots can be updated after initial render.

[github-actions]

View your branch deployment here: https://mi6.github.io/ic-ui-kit/branches/feat/266-enable-typescript-strict-mode-2/web-components
View your React branch deployment here: https://mi6.github.io/ic-ui-kit/branches/feat/266-enable-typescript-strict-mode-2/react