[WTF-2485]: Remove enzyme from widget generator in preparation of React 19

[LEGIO-SEXTA-FERRATA]

Checklist

• Contains unit tests ✅
• Contains breaking changes ✅
• Compatible with: MX 1️⃣1️⃣
• Did you update version and changelog? ❌
• PR title properly formatted ([XX-000]: description)? ✅

This PR contains

• Bug fix
• Feature
• Refactor
• Documentation
• Other (describe)

What is the purpose of this PR?

This PR prepares the Yeoman widget generator for replacing the Enzyme for testing in favor of RTL, the React Testing Library.

Relevant changes

• The generator for web package.json is adjusted to remove enzyme as a dependency
• The react-dom dependency is added to resolutions and overrides as RTL required it
• The scaffolded unit tests when the user chooses the unit test option are adjusted for RTL
• Generator tests are adjusted
• A bonus fix for updating the copyright year is included.

What should be covered while testing?

• Both the options with unit test and e2e should be tested
• The generator tests must be green
• The default tests that arrive with a scaffolded widget should be green

REMAINING:

• Check native
• Check e2e tests
• PWT Workflow Actions seems to be failing for the PR
• One issue is that, the scaffolded widget is not able to run the unit tests before npm install is run
• Check if we can get rid of the non-enzyme config in PWT
• Add a check in PWT to detect and warn on enzyme tests (grepping on enzyme imports will do probably)
• Mention as breaking change in release notes
• Check docs

[mlaponder]

When running unit tests on a generated widget from the command line I get the following error:

AIL  src/components/__tests__/HelloWorldSample.spec.tsx
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

[mlaponder]

Shouldn't we update versions on generator and pluggable widgets tools ?