@mf-types. expose typings for shared modules

Clear and concise description of the problem

In v2, the plugin bundles only typings for exposed code + typings for 3-rd party modules that are used in the exposed code.

Suggested solution

Would be great to add an option to also expose typings for shared modules.

Alternative

No response

Additional context

No response

Validations

• [X] Read the Contributing Guidelines.
• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

This could be problematic since there may be multiple shared modules at different versions provided. I would only be able to implement one at random, any change in version or contract between the remotes would not work since 'react' for example is the only identifier. unlike exposed modules which have a unique namespace like app1/react

Stale issue message