feat: root components are grouped by envs and apps

[zkochan]

Proposed Changes

• This PR changes how the root components feature is working.
• From now on if the root components feature is enabled, Bit will generate a folder called .bit_roots in the root of your node_modules folder.
  This folder will contain a sub-folder for 2 entities:

1. each env that is used by at least one of your components in the workspace
2. any app existing in your workspace.
   These folders under the .bit_roots are called root components. each one of them represents a root.

• Each root will have links to all components in the workspace with the peer dependencies resolved from the root entity.
  for example, if you have an env that sets React to v18 and another root that sets React to v17, the version of react will be determined by the version of the root component.
  so a button created in the react 17 env when used inside a composition of components created by a react 18 env will get react v18 at runtime.
  While in the composition of itself, it will get react 17 at runtime.

• Here is an example of the top level structure of the .bit_roots folder when root components is enabled

- Here is an example of the structure of one of the root components

• enable "rootComponents" by setting the following in the workspace.jsonc

"teambit.dependencies/dependency-resolver": {
    "rootComponents": true,
}