feat(sdk): fix SDK React secondary entry points

[rjvelazco]

Nx and TypeScript docs References

• Define Secondary Entry Points for TypeScript Packages.
• Module Resolution - moduleResolution
• typesVersions

Explanation

This pull request includes various updates to the SDK packages in the core-web/libs directory, focusing on version upgrades and configuration improvements.

Version upgrades:

• core-web/libs/sdk/client/package.json: Updated the version from 0.0.1-alpha.38 to 0.0.1-beta.2.
• core-web/libs/sdk/experiments/package.json: Updated the version from 0.0.1-alpha.38 to 0.0.1-beta.2.
• core-web/libs/sdk/react/package.json: Updated the version from 0.0.1-alpha.38 to 0.0.1-beta-2.
• core-web/libs/sdk/uve/package.json: Updated the version from 0.0.1 to 0.0.1-beta.2.

Configuration improvements:

• core-web/libs/sdk/experiments/tsconfig.json: Added target, module, and moduleResolution options to the TypeScript configuration.
• core-web/libs/sdk/react/package.json: Added an exports field to specify entry points for the package.
• core-web/libs/sdk/react/project.json: Updated the Rollup configuration to include main, additionalEntryPoints, and generateExportsField options.
• core-web/libs/sdk/react/tsconfig.json: Updated the include field to encompass various file types.
• core-web/libs/sdk/react/tsconfig.lib.json: Expanded the include field to cover additional directories and file types.

Video

fix-video-31178-sdk-react-fix-secondary-entry-points.mov

This PR fixes: #31178

[fmontes]

Approve with some questions.

[KevinDavilaDotCMS]

To solve the moduleResolution: node issue, ee decided to use typesVersions, which allows us to create subpaths under this module resolution approach and does not affect projects that use a different moduleResolution.

typesVersion doc