feat(build): add support for Create React App without eject

[char0n]

Description

This is an effort to make our primary ESM bundle work out of the box with CRA@5 (Create React App). After this PR is merged it gives us operational space to progressively eliminate (or replace by others more modern polymorphic ones) dependencies using Node.js API which needs to be poly-filled.

Requirements:

• primary fragment must work out of the box with CRA@5 without errors or warnings
• primary fragment must work with webpack@4
• primary fragment must work with webpack@5
• primary fragment must work with Jest

Refs #7898
Refs #7944
Refs #7935
Refs #7910
Refs #7908
Refs #7902

Motivation and Context

Currently we have to have quite complex resolve.fallbacks and use of ProvidePlugin to build the SwaggerUI successfully. Having primary ESM bundle being able to build with industry standard build systems without any additional configuration would be a huge gain and lower the adoption of SwaggerUI integrations.

How Has This Been Tested?

Manually with CRA@5

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.